Mempalace Http
FreeNot checkedEnables remote access to the MemPalace MCP server via HTTP, supporting bearer token authentication and concurrent clients while exposing all mempalace tools.
About
Enables remote access to the MemPalace MCP server via HTTP, supporting bearer token authentication and concurrent clients while exposing all mempalace tools.
README
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.
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.Lockserializes 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"}
Installing Mempalace Http
This server has no published package — it is built from source. Open the repository and follow its README.
▸ github.com/flejz/mempalace-mcp-httpFAQ
Is Mempalace Http MCP free?
Yes, Mempalace Http MCP is free — one-click install via Unyly at no cost.
Does Mempalace Http need an API key?
No, Mempalace Http runs without API keys or environment variables.
Is Mempalace Http hosted or self-hosted?
A hosted option is available: Unyly runs the server in the cloud, no local setup required.
How do I install Mempalace Http in Claude Desktop, Claude Code or Cursor?
Open Mempalace Http on unyly.org, pick your client tab (Claude Desktop, Claude Code, Cursor) and press Install — the config is generated automatically, no JSON editing.
Related MCPs
GitHub
PRs, issues, code search, CI status
by GitHubFilesystem
Secure file operations with configurable access controls.
Memory
Knowledge graph-based persistent memory system.
Template MCP Server
A CLI tool to create a new Model Context Protocol server project with TypeScript support, dual transport options, and an extensible structure
by mcpdotdirectCompare Mempalace Http with
Not sure what to pick?
Find your stack in 60 seconds
Author?
Embed badge for your README
Browse similar
All development MCPs
