Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Persistent memory for AI agents — log and recall conversation context over MCP.
Pick the AI app you use, then copy the settings.
Passed 5/5 checks · What you ask goes through the maker’s server (synap-mcp.maximem.ai)
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 5 min
You need a Synap Memory key (create it on the maker’s site) · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
Synap Memoryhttps://synap-mcp.maximem.ai/mcpUnder Request headers, add this name and value
AuthorizationBearer <paste your key here>Paste the key only into the app’s field, never into a chat or to anyone
Leave Authentication as Claude detected it, then click Add
+ConnectorsSynap Memory
Use Synap Memory and tell me what you can do for me, then show me one thing✓ If Claude says it is using Synap Memory or shows a Synap Memory tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Synap Memory yet
Synap Memory needs your own key to connect, but OpenAI’s help page only describes OAuth sign-in; there is no key option we could verify
A · Use an app that can connect Synap Memory
B · Others in Search & AI memory that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code · about 5 min
You need a Synap Memory key (create it on the maker’s site)
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user synap https://synap-mcp.maximem.ai/mcp --header 'Authorization: Bearer your-value'Replace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see Synap Memory listed as connected
Use Synap Memory and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Synap Memory or shows a Synap Memory tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 5 min
You need a Synap Memory key (create it on the maker’s site)
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
In the Synap Memory settings, Authorization is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Synap Memory and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Synap Memory or shows a Synap Memory tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 5 min
You need a Synap Memory key (create it on the maker’s site)
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
In the Synap Memory settings, Authorization is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Synap Memory and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Synap Memory or shows a Synap Memory tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://synap-mcp.maximem.ai/mcpJSON settings are under “For developers” below
Claude Code
claude mcp add --transport http --scope user synap https://synap-mcp.maximem.ai/mcp --header 'Authorization: Bearer your-value'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"synap": {
"url": "https://synap-mcp.maximem.ai/mcp",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"synap": {
"type": "http",
"url": "https://synap-mcp.maximem.ai/mcp",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Tool names and descriptions exactly as the server reported them on Nov 11, 2026. The maker wrote them, not us; we show them as plain text.
log_exchangeAfter 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 st
check_memory_statusCheck 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 ingest
recall_contextBefore 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 B2
list_recent_memoriesList 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.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 12, 2026
The registry name was verified against the domain maximem.ai (the registry checks domain ownership)
Code last changed 7 days ago
Uses Apache-2.0
Responded in 379 ms (HTTP 200)
No sign-in needed
Read 4 tool descriptions and found no hidden instructions to the AI
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 5 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: Authorization
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed 7 days ago, and the latest version (0.1.0) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT Business and above.
In the same category: Context7, Codebase Memory, Ruflo
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Agent teams, swarms, memory and hooks for Claude Code and Codex, served over MCP.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Hosted remote MCP server (Streamable HTTP) that re-fronts the existing Synap public REST operations as MCP tools, so no-code platforms (Gumloop, n8n) can give their agents persistent memory with nothing but a pasted MCP URL and a Bearer token.
It is a stateless adapter — no new backend, storage, or pipeline. Each tool call maps to one existing REST operation, and the incoming Bearer synap_ token is forwarded verbatim to synap-cloud, which owns auth.
https://synap-mcp.maximem.ai/mcphttps://synap-mcp.maximem.ai/health| Tool | REST operation | Notes | ||
|---|---|---|---|---|
log_exchange | POST /api/v1/memories/create (mode=long-range) | Forward every turn; extraction decides what persists. user_id scopes per end-user, customer_id is B2B only (see Scoping); optional conversation_id. | ||
recall_context | `POST /v1/context/{client\ | user\ | customer}/fetch (mode=fast`) | Hot path; no IDs ⇒ client scope. customer scope is B2B only. |
list_recent_memories | broad /v1/context/.../fetch (no query) | Debug / "test my memory". Same scoping rules. | ||
check_memory_status | GET /api/v1/memories/status/{id} | Takes no scope ids: the ingestion_id already identifies the write. |
The REST API enforces this. It is not advice, and it has been live on production since 2026-08-26 07:07 UTC.
Instance mode (user_context_isolation) | What to send | What happens otherwise |
|---|---|---|
equals_customer (B2C) | user_id and nothing else. The user id is the whole identity. | Any customer_id is rejected with HTTP 400. /v1/context/customer/fetch is not available at all. |
strict (B2B) | customer_id is required, alongside user_id. | A user_id on its own is an error. Unchanged by this contract. |
GET /api/v1/auth/whoami reports the mode as user_context_isolation. This server reads it once per token and refuses a customer_id locally on a B2C instance, so a model gets a sentence telling it what to send instead of a status code it cannot act on. If the mode cannot be read, nothing is refused and the API stays authoritative.
Pass no IDs at all ⇒ client scope (shared per credential), which is valid in both modes. Note: client-scope writes are not surfaced on the dashboard Memories page (relational), so per-user scoping is recommended when dashboard visibility matters. Fill user_id from an n8n expression / Gumloop input, and pass the same value on log_exchange and recall_context so writes and reads address the same person.
Host header. The server disables the MCP transport's DNS-rebinding check (it sits behind a proxy + Bearer auth), so any reverse proxy can forward the real Host — no Host-rewrite hack needed.
pip install -e ".[dev]"
SYNAP_API_URL=http://localhost:8000 uvicorn synap_mcp_server.server:app --port 8090 curl http://localhost:8090/health # {"status":"ok",...}
An MCP server is not an agent. It exposes tools to somebody else's agent and is handed one stateless HTTP call at a time, so most of what an agent does is invisible here: the caller's tool calls, its tool results and its reasoning never reach this process, and nothing tells a stateless server that a conversation has ended. Those are not reported, because there is nothing to report.
The turn does exist. log_exchange is handed the user's message and the assistant's reply as arguments. Set MCP_STREAM_EVENTS=true and each logged exchange is also reported as a conversation turn on POST /v1/events/batch, the HTTP door onto the same listening path the gRPC stream feeds, so the anticipation agent sees the turn and not only the memory extracted from it. This server does not use the SDK's gRPC stream, as the other integrations do: it holds no SDK, keeps no state between requests, and every request can carry a different tenant's key, so a stream per key would be an unbounded pool of connections that nothing closes. Moving it onto the SDK would be a rewrite of its transport for a caller that has no use for what the stream brings back.
Nor does it replace anything of Synap's compaction: the caller's agent keeps its own history and no tool here returns a conversation.
It is off by default, on purpose. Turning it on adds a second backend call per log_exchange, writes the turn to conversation history in addition to the long-range document, and runs the anticipation agent, which bills model calls.
It is not on by default for a second reason. Synap extracts from a conversation when it is compacted, which starts once ten messages have been recorded. Recording every exchange as turns *instead of* the long-range document would hold the memory back until then (the next recall_context finds nothing, and there is no ingestion_id to check); recording them *as well* extracts each exchange twice.
What does not change either way: log_exchange still queues the long-range document and still returns the ingestion_id that check_memory_status and wait_for_processing are built on. A turn report is best effort and can never alter what a tool answers. A turn with no user_id or no conversation_id is not reported at all, because the events route requires both.
pip install -e ".[dev]"
pytest -q
| Var | Default | Meaning |
|---|---|---|
SYNAP_API_URL | http://synap-cloud:8000 | Backing REST API base URL (internal docker hostname in prod). |
MCP_PORT | 8090 | Listen port. |
MCP_RECALL_TIMEOUT_S | 10 | Recall (read) timeout. |
MCP_INGEST_TIMEOUT_S | 8 | Log/ingest (write) timeout. |
MCP_DEFAULT_MAX_RESULTS | 10 | Default recall result count. |
MCP_STREAM_EVENTS | false | Also report a logged exchange as a conversation turn for anticipation. See above before enabling. |
MCP_EVENTS_TIMEOUT_S | 4 | Turn-report timeout. Best effort; a miss never changes a tool's answer. |
LOG_LEVEL | INFO | Log level. |
ENVIRONMENT | production | Reported in /health. |
No Synap API key is configured on the server — the end user's key arrives per-request as a Bearer token.
See the Synap MCP documentation for platform setup guides (Gumloop, n8n) and deployment details.