Skip to main content
Glama
flejz

mempalace-mcp-http

by flejz

mempalace-mcp-http

HTTP transport for mempalace-mcp. One palace, many machines.

Prerequisites

mempalace must already be installed on the target machine:

uv tool install mempalace   # or: pip install mempalace

This tool extends mempalace — does not replace or install it.

Related MCP server: Levitate

Setup

curl -fsSL https://raw.githubusercontent.com/flejz/mempalace-mcp-http/master/setup.sh | bash

Or clone and run:

git clone https://github.com/flejz/mempalace-mcp-http
cd mempalace-mcp-http
./setup.sh

Detects mempalace, installs HTTP deps, configures systemd service. If ~/.claude/settings.json exists, prompts to add (or replace existing mempalace entry with) the HTTP MCP config automatically.

Token management

mempalace-token is installed to ~/.local/bin/ during setup:

mempalace-token show      # masked preview
mempalace-token reveal    # full token
mempalace-token rotate    # new token + restart service
mempalace-token remove    # invalidate token — blocks all clients

remove replaces the token with an unguessable value (server stays auth-required, no valid token exists). Use rotate to recover access.

Claude Code config

Setup auto-configures via claude mcp add with a confirmation prompt. Manual command on any machine:

claude mcp add --transport http mempalace \
  http://<palace-host>:8765/mcp \
  --header "Authorization: Bearer <token>"

Replaces the standard stdio entry (python -m mempalace.mcp_server) — setup.sh detects it and prompts automatically.

For non-Claude clients, equivalent settings.json entry:

{
  "mcpServers": {
    "mempalace": {
      "type": "http",
      "url": "http://<palace-host>:8765/mcp",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

Env vars

Var

Default

Purpose

MEMPALACE_HTTP_PORT

8765

Listen port

MEMPALACE_HTTP_HOST

0.0.0.0

Bind address

MEMPALACE_HTTP_TOKEN

(unset = open)

Bearer auth token

How it works

  • Calls mempalace.mcp_server.handle_request() directly — no subprocess, no protocol proxying

  • threading.Lock serializes all calls — sqlite-safe under concurrent clients

  • 1:1 tool mapping — all mempalace tools available, auto-updated when mempalace upgrades

Health check

curl http://localhost:8765/health
# {"status":"ok","mempalace":"3.x.x"}

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

No tool schema history has been recorded yet.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • F
    license
    Not graded
    quality
    C
    maintenance
    HTTP bridge that exposes MCP tools via POST endpoint, enabling remote LLMs to access local functionality with bearer authentication.
    -
  • A
    license
    Not graded
    quality
    A
    maintenance
    Lifts local stdio MCP servers into remote Streamable HTTP endpoints for cloud-hosted AI clients, with bearer-token auth and tool policy filtering.
    11
    MIT
  • F
    license
    Not graded
    quality
    B
    maintenance
    This MCP server provides a Streamable HTTP endpoint with bearer token authentication, exposing echo and add tools, and an info resource for remote client integration.
    -

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/flejz/mempalace-mcp-http'

If you have feedback or need assistance with the MCP directory API, please join our Discord server