mcp server
Synap Memory
Persistent memory for AI agents — log and recall conversation context over MCP.
Description as published by the maintainer. Source
- version 0.1.0
- active
- memory and context
active — Most recent push to the repository was 2026-08-06. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
4 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
check_memory_status(ingestion_id)- Check 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). Required: ingestion_id.
list_recent_memories(user_id, customer_id, max_results)- List recent things remembered about this user. Useful for debugging or to confirm that memory is working. Pass user_id/customer_id to scope to one person.
log_exchange(user_id, customer_id, user_message, conversation_id, assistant_message, wait_for_processing)- After 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 (or an organization id as customer_id) so each person's memory stays separate; if every conversation is the same single user, omit them. Logging is fire-and-forget by default; set wait_for_processing=true only when you need to confirm the memory finished extracting before continuing. Required: user_message.
recall_context(query, user_id, customer_id, max_results)- Before 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 (or customer_id) you log with so you recall the right person's memory. Required: query.
Last successful function declaration observed on . Source: https://synap-mcp.maximem.ai/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://synap-mcp.maximem.ai/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 58 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-06 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 2 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-22 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | Apache-2.0 | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-07-22 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub | |
| mcp tools declared | 4 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | synap-mcp.maximem.ai | |
| mcp endpoint status | ok | The server listed 4 functions when asked. | as of probe | synap-mcp.maximem.ai |
Where to get it
Related, by what their authors tagged them
-
io.github.Beever-AI/beever-atlas
— last commit 2026-08-06, shares agent-memory, google-adk
Open-source LLM knowledge base: team chat into a typed knowledge graph and auto-generated wiki.
-
Agent Coherence — Stale Write Guard (FS)
— last commit 2026-07-21, shares agent-memory, autogen, crewai
Coherence guard for shared files: denies stale writes so agents don't silently overwrite each other.
-
com.memxus/memxus
— last commit 2026-07-30, shares ai-memory, memory, memory-layer
Persistent memory layer that saves and recalls your project context and preferences.
-
io.github.enrichgateagent-png/beacon-mcp
— last commit 2026-07-13, shares autogen, crewai, langchain
Search 17,900+ open-source AI agents by capability, ranked by GitHub traction. Free, no key.
-
io.github.HBarefoot/engram
— last commit 2026-07-07, shares ai-memory, memory-layer
Local-first persistent memory for AI agents — SQLite + local embeddings, MCP-native, no cloud.
-
io.github.hidai25/evalview-mcp
— shares autogen, crewai
Regression testing for AI agents. Golden baselines, CI/CD, LangGraph, CrewAI, OpenAI, Claude.
-
BrowseAI Dev
— last commit 2026-08-02, shares crewai, langchain, llamaindex
Evidence-backed web research for AI agents with citations and confidence scores.
-
io.github.darknodebros/elesync
— last commit 2026-08-05, shares ai-memory, conversational-ai
Local-first MCP memory vault: files you own, shared across ChatGPT, Claude, Gemini & any MCP client
-
Perspective AI
— last commit 2026-04-28, shares conversational-ai
An AI concierge that turns static forms into adaptive AI conversations. From any MCP client.
-
io.github.Adgentek/adsmcp
— last commit 2026-05-28, shares conversational-ai
MCP-native ad server. Monetize AI chatbots and agents with conversational ads.
These share tags the maintainers applied themselves, such as agent-memory, google-adk, autogen, crewai. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: agent-memory, ai, ai-agents, ai-memory, autogen, context, conversational-ai, crewai, google-adk, haystack, langchain, llamaindex, llm, long-term-memory, memory, memory-layer.
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json