hybrid-memory-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@hybrid-memory-mcpsearch memories about project ideas"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
hybrid-memory-mcp
Universal FastMCP bridge into a hybrid memory stack. Any MCP-capable agent harness (Claude Code, Codex, RooCode, OpenClaw, Pi) adds one streamable-HTTP URL + bearer token and gains four tools against the SAME memory the host agent uses.
OpenViking (primary, read+write) —
mem_save,mem_search,mem_readHoncho (secondary, read-only reasoning) —
mem_recall
Endpoint
URL: http://<HOST>:8899/mcp (bind a private LAN/VPN IP — not public)
Auth: Authorization: Bearer <HMCP_BEARER_TOKEN from .env>
Transport: streamable-http<HOST> is set via HMCP_BIND_HOST in .env (defaults to 127.0.0.1). Bind it
to a private tailnet/LAN IP so only trusted machines on your network can reach it —
this server is not designed for public internet exposure.
Related MCP server: Synapto
Tools
tool | args | backend |
| content (req), category, source_agent | OV disk-write + async index |
| query (req), limit=8 | OV |
| uri (req, must start | OV |
| query (req) | Honcho |
category enum: pattern | entity | event (default) | preference.
Every saved fact is footer-tagged [via: <source_agent>] for cross-harness attribution.
Configuration (.env, chmod 0600)
HMCP_BEARER_TOKEN=<generate: python3 -c "import secrets;print('hmcp_'+secrets.token_urlsafe(32))">
HMCP_BIND_HOST=127.0.0.1 # set to your private tailnet/LAN IP
HMCP_BIND_PORT=8899
OPENVIKING_ENDPOINT=http://127.0.0.1:1933
HONCHO_BASE_URL=http://localhost:8000
HONCHO_WORKSPACE=hermes
HONCHO_PEER=<your-peer-id>Client config
Replace <TOKEN> with the value of HMCP_BEARER_TOKEN, and <HOST> with your bind IP.
Claude Code
claude mcp add --transport http hybrid-memory http://<HOST>:8899/mcp \
--header "Authorization: Bearer <TOKEN>"Codex (~/.codex/config.toml)
[mcp_servers.hybrid_memory]
url = "http://<HOST>:8899/mcp"
http_headers = { Authorization = "Bearer <TOKEN>" }Generic streamable-http (RooCode / OpenClaw / Pi / any MCP client)
{
"mcpServers": {
"hybrid-memory": {
"type": "streamable-http",
"url": "http://<HOST>:8899/mcp",
"headers": { "Authorization": "Bearer <TOKEN>" }
}
}
}Run
python3 -m venv venv && ./venv/bin/pip install -r requirements.txt
./venv/bin/python server.py # binds $HMCP_BIND_HOST:$HMCP_BIND_PORT, mounts /mcpFor production, run under a supervisor with restart-on-failure (systemd unit,
Restart=always).
Checks
bash specs/hybrid-memory-mcp/checks/roundtrip.sh # C3 save->search->read (server stopped)
bash specs/hybrid-memory-mcp/checks/validation.sh # C6 input-validation (server stopped)
bash specs/hybrid-memory-mcp/checks/auth.sh # C4 bearer enforced (spins ephemeral server)
bash specs/hybrid-memory-mcp/checks/mcp_handshake.sh # C8 MCP initialize handshake
bash specs/hybrid-memory-mcp/checks/restart.sh # C7 supervised persistence (after unit installed)Design notes
Async index waiting-list. OV's
content/writeruns the semantic+vector index inline behind one global write lock (~40s/write).mem_savedoes the durable part synchronously (write the file to disk — the memory is persisted and recoverable immediately) and hands the slow index to a background worker that drains one job at a time. Saves return in <10ms; search visibility follows asynchronously.Crash-durable queue. Each queued index job drops a pending-marker on disk; the worker deletes it after a successful index; on startup any survivors are re-queued. A
kill -9with items in flight loses nothing — markers reconcile on restart, and the worker also re-enqueues on transient failure so it self-heals once OV recovers.OV 0.3.8 create-mode bug.
content/writecannot CREATE new files, somem_savewrites the file to the local store first, thencontent/write mode=replaceto index.Graceful degradation.
mem_recallreturns{"status": "honcho unavailable", ...}instead of crashing when Honcho is down or slow.
This server cannot be deployed
Maintenance
Related MCP Connectors
- KogniteOAuthdev.kognite
Hosted agent memory: store, search, and recall facts across sessions from any MCP client.
Persistent personal memory for AI assistants — save, search, and recall across every MCP client.
- MemocoreOAuthai.memocore
Shared memory for all your AI agents, your whole team and every MCP client — save, search, recall.
Persistent memory for AI agents to retain, retrieve, and recall conversation context through MCP.
Related MCP Servers
- AlicenseNot gradedqualityNot gradedmaintenanceIntegrates the Mem0 Memory API with MCP-compatible clients to provide AI agents with persistent, long-term memory capabilities. It enables users to add, search, update, and delete memories to maintain context and personalization across different interactions.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceProvides persistent, searchable memory for MCP-compatible agents, enabling recall by meaning, automatic decay, trust scoring, and cross-agent handoffs.5MIT
- AlicenseAqualityDmaintenanceProvides persistent memory with semantic search for MCP-based AI agents, enabling them to store and recall information across sessions using vector embeddings.41MIT
- AlicenseNot gradedqualityDmaintenanceLocal-first AI memory layer with hybrid retrieval and brain-inspired namespaces. Enables agents to save, search, and manage memories directly via MCP tools.3 npmMIT