mempalace-mcp-http
Enables remote access to the MemPalace MCP server via HTTP, supporting bearer token authentication and concurrent clients while exposing all mempalace tools.
README
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.
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"}
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.