mempalace-mcp-http
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
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 mempalaceThis 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 | bashOr clone and run:
git clone https://github.com/flejz/mempalace-mcp-http
cd mempalace-mcp-http
./setup.shDetects 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 clientsremove 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 |
|
| Listen port |
|
| Bind address |
| (unset = open) | Bearer auth token |
How it works
Calls
mempalace.mcp_server.handle_request()directly — no subprocess, no protocol proxyingthreading.Lockserializes all calls — sqlite-safe under concurrent clients1: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.
Loading tool schema changelog…
Related MCP Connectors
Remote MCP server exposing SMI Aware tools, resources, and skills over Streamable HTTP.
Remote MCP server exposing your Node Command fleet (files, shell, processes, browser) to AI hosts.
Remote MCP server for supportsheep: run AI interviews and manage support content for your blog.
Remote MCP server for supportsheep: run AI interviews and manage support content for your blog.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceHTTP bridge that exposes MCP tools via POST endpoint, enabling remote LLMs to access local functionality with bearer authentication.ISC
- AlicenseNot gradedqualityBmaintenanceLifts local stdio MCP servers into remote Streamable HTTP endpoints for cloud-hosted AI clients, with bearer-token auth and tool policy filtering.12 npmMIT
- FlicenseNot gradedqualityFmaintenanceEnables remote MCP clients to securely access AgentMemory tools like memory_recall, memory_smart_search, and memory_save through OAuth 2.1 and Streamable HTTP, while keeping the AgentMemory backend secret private.-
- FlicenseNot gradedqualityCmaintenanceEnables remote use of MaIGIC tools such as determine_hamiltonian and compute_property over Streamable HTTP with bearer-token authentication, allowing clients like Cursor to access them from any machine.-