Synap Memory MCP server
online · 100% uptimeai.maximem/synap·v0.1.0·74 starsPersistent memory for AI agents — log and recall conversation context over MCP.
74 stars
Reviews
Write oneNobody has reviewed Synap Memory yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Synap Memory tools (4)
write = sends, deletes, buys or postscheck_memory_statusFreeCheck whether a logged exchange has finished processing. Pass the ingestion_id returned by log_exchange. Returns the processing status and how many memories were extracted. Useful to confirm a save completed (extraction is asynchronous). Takes no user_id or customer_id: an ingestion_id already identifies the write, so the identifier contract does not apply here.
list_recent_memoriesFreeList recent things remembered about this user. Useful for debugging or to confirm that memory is working. Pass user_id to scope to one person. SCOPING: customer_id is B2B ONLY. On a B2B instance (user_context_isolation=strict) it is REQUIRED and a user_id on its own is an error. On a B2C instance (user_context_isolation=equals_customer) it is NOT accepted: the API rejects it with HTTP 400, customer-scoped retrieval does not exist there, and user_id is the whole identity. If you do not know which mode this instance is in, send user_id only and no customer_id; GET /api/v1/auth/whoami reports the mode as user_context_isolation.
log_exchangeFreeAfter each user message, send the exchange here so it can be remembered. You do not need to decide what is important, just forward the user message (and your reply, if you have one) and Synap will keep what matters. If your app serves more than one end-user, pass that person's stable id as user_id so each person's memory stays separate; if every conversation is the same single user, omit it. SCOPING: customer_id is B2B ONLY. On a B2B instance (user_context_isolation=strict) it is REQUIRED and a user_id on its own is an error. On a B2C instance (user_context_isolation=equals_customer) it is NOT accepted: the API rejects it with HTTP 400, customer-scoped retrieval does not exist there, and user_id is the whole identity. If you do not know which mode this instance is in, send user_id only and no customer_id; GET /api/v1/auth/whoami reports the mode as user_context_isolation. Logging is fire-and-forget by default; set wait_for_processing=true only when you need to confirm the memory finished extracting before continuing.
recall_contextFreeBefore replying, call this to recall anything already known about this user from past conversations. Use the user's latest message as the query. If you serve multiple end-users, pass the same user_id you log with so you recall the right person's memory. SCOPING: customer_id is B2B ONLY. On a B2B instance (user_context_isolation=strict) it is REQUIRED and a user_id on its own is an error. On a B2C instance (user_context_isolation=equals_customer) it is NOT accepted: the API rejects it with HTTP 400, customer-scoped retrieval does not exist there, and user_id is the whole identity. If you do not know which mode this instance is in, send user_id only and no customer_id; GET /api/v1/auth/whoami reports the mode as user_context_isolation.
Public scan report
scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 672ms20/20
- Tool poisoning4 tool descriptions checked15/15
- Auth qualityAPI key sent as a header8/15
- Maintenancelast push 0 days ago15/15
- Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace8/10
How Synap Memory compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
- Tools
- 4
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 301 ms
- faster than 48% of 30,031 servers
- GitHub stars
- 74
- more than 95% of 28,688 servers
What its tools let an agent do: 4 read
Install Synap Memory in Claude Code, Cursor or VS Code
claude mcp add --transport http synap https://synap-mcp.maximem.ai/mcp
What the publisher says
From the Synap Memory repository's README, as published. We do not edit it. Read it on GitHub
<!-- This README is the SINGLE SOURCE OF TRUTH, maintained in the private monorepo at publicsdk/README.md and synced to the public repo root by scripts/synctopublic.sh. DO NOT edit the copy in maximem-ai/maximemsynapsdk directly: changes there are overwritten on the next sync. Edit here instead. The integration table below is generated by scripts/genreadme_integrations.py. -->
Docs · Dashboard · Benchmarks · Website
The memory layer for production AI agents
Your AI agents forget everything between conversations. Synap fixes that with a production-grade memory layer built for applications that serve real users at scale. #1 on LongMemEval (92%) and LoCoMo (93.2%), sub-15ms anticipatory retrieval, and native integrations with every major AI framework.
LangChain · LangGraph · LlamaIndex · CrewAI · AutoGen · Haystack · Google ADK · OpenAI Agents · Semantic Kernel · Pydantic AI · Agno · LiveKit · Pipecat · Claude Agent · Mastra · Vercel AI SDK · NeMo Agent Toolkit · Microsoft Agent Framework
What's in this repo: the open-source Python and JavaScript SDKs plus all framework integrations, licensed under Apache 2.0. The Synap memory engine itself (ingestion, entity resolution, retrieval, anticipation) runs as a fully managed cloud service operated by Maximem and is not open source. The SDKs in this repo are clients for that service; there is nothing to self-host, and an API key is required.
Benchmarks
Synap leads the field on the two standard long-term memory benchmarks, evaluated on identical hardware with an open-source harness.
Synap outperforms leading published memory systems, run through the same open-source evaluation harness on identical hardware and configs.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Synap Memory: common questions
- Is Synap Memory MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Synap Memory safety report
- How do I install Synap Memory?
- It runs remotely at synap-mcp.maximem.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Synap Memory need an API key?
- Yes. The registry entry asks for
Authorization. - Is Synap Memory maintained?
- The last commit was 40 days ago (2026-09-25). The latest release is v0.1.0.
- Is Synap Memory up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of Synap Memory?
- Servers from other publishers that do the same job: Deja Vu MCP server, State Memory MCP server and Knowl MCP server. Compare all Synap Memory alternatives.
- How does Synap Memory compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Synap Memory
Same job from other publishers: the closest match first, then the best rated.
- Deja Vudeja-vu: local memory over the session histories of forty-three coding agents.not reviewedEstablishedA
State Memory MCPPersistent workflow graph server tracking tasks, decisions, spatial entities, and blockers.not reviewedEstablishedA
KnowlPersistent memory for AI agents, for code, research and everyday life. Stale facts retire.not reviewedEstablishedA