MCP Server
Synap Memory
ai.maximem/synap
What this MCP does
Stores and recalls persistent conversational context for AI agents.
Capabilities
Tools
4
tools
check_memory_status
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). Takes no user_id or customer_id: an ingestion_id already identifies the write, so the identifier contract does not apply here.
Input schema
{'type': 'object', 'title': 'check_memory_statusArguments', 'required': ['ingestion_id'], 'properties': {'ingestion_id': {'type': 'string', 'title': 'Ingestion Id'}}}
Output schema
{'type': 'object', 'title': 'check_memory_statusOutput', 'required': ['result'], 'properties': {'result': {'type': 'string', 'title': 'Result'}}}
list_recent_memories
List 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.
Input schema
{'type': 'object', 'title': 'list_recent_memoriesArguments', 'properties': {'user_id': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'User Id', 'default': None, 'description': 'Stable id of the end-user this call belongs to. On a B2C instance this is the ONLY identifier you send and it is the whole identity. On a B2B instance send it together with customer_id. Omit both if every conversation is the same single user.'}, 'customer_id': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Customer Id', 'default': None, 'description': 'B2B ONLY. Required on a B2B instance (user_context_isolation=strict), where a user_id on its own is an error. NOT accepted on a B2C instance (user_context_isolation=equals_customer): the API rejects it with HTTP 400 and there is no customer scope to read from. When in doubt leave this out and send user_id alone. GET /api/v1/auth/whoami reports the mode.'}, 'max_results': {'type': 'integer', 'title': 'Max Results', 'default': 10}}}
Output schema
{'type': 'object', 'title': 'list_recent_memoriesOutput', 'required': ['result'], 'properties': {'result': {'type': 'string', 'title': 'Result'}}}
log_exchange
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 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.
Input schema
{'type': 'object', 'title': 'log_exchangeArguments', 'required': ['user_message'], 'properties': {'user_id': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'User Id', 'default': None, 'description': 'Stable id of the end-user this call belongs to. On a B2C instance this is the ONLY identifier you send and it is the whole identity. On a B2B instance send it together with customer_id. Omit both if every conversation is the same single user.'}, 'customer_id': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Customer Id', 'default': None, 'description': 'B2B ONLY. Required on a B2B instance (user_context_isolation=strict), where a user_id on its own is an error. NOT accepted on a B2C instance (user_context_isolation=equals_customer): the API rejects it with HTTP 400 and there is no customer scope to read from. When in doubt leave this out and send user_id alone. GET /api/v1/auth/whoami reports the mode.'}, 'user_message': {'type': 'string', 'title': 'User Message'}, 'conversation_id': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Conversation Id', 'default': None}, 'assistant_message': {'type': 'string', 'title': 'Assistant Message', 'default': ''}, 'wait_for_processing': {'type': 'boolean', 'title': 'Wait For Processing', 'default': False}}}
Output schema
{'type': 'object', 'title': 'log_exchangeOutput', 'required': ['result'], 'properties': {'result': {'type': 'string', 'title': 'Result'}}}
recall_context
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 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.
Input schema
{'type': 'object', 'title': 'recall_contextArguments', 'required': ['query'], 'properties': {'query': {'type': 'string', 'title': 'Query'}, 'user_id': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'User Id', 'default': None, 'description': 'Stable id of the end-user this call belongs to. On a B2C instance this is the ONLY identifier you send and it is the whole identity. On a B2B instance send it together with customer_id. Omit both if every conversation is the same single user.'}, 'customer_id': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Customer Id', 'default': None, 'description': 'B2B ONLY. Required on a B2B instance (user_context_isolation=strict), where a user_id on its own is an error. NOT accepted on a B2C instance (user_context_isolation=equals_customer): the API rejects it with HTTP 400 and there is no customer scope to read from. When in doubt leave this out and send user_id alone. GET /api/v1/auth/whoami reports the mode.'}, 'max_results': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Max Results', 'default': None}}}
Output schema
{'type': 'object', 'title': 'recall_contextOutput', 'required': ['result'], 'properties': {'result': {'type': 'string', 'title': 'Result'}}}
History
Recent tool changes
Added
list_recent_memories
Sept. 17, 2026, 7:57 a.m.
Added
recall_context
Sept. 17, 2026, 7:57 a.m.
Added
check_memory_status
Sept. 17, 2026, 7:57 a.m.
Added
log_exchange
Sept. 17, 2026, 7:57 a.m.
Discover
Similar MCP servers
Delx Commerce — Pay-per-Result APIs for Agents
io.github.davidmosiah/delx-mcp-a2a
Provides pay-per-result APIs and agent protocol tools for continuity, multi-agent coordination, document OCR, and crypto-related …
SAP MCP Server
ai.oobeprotocol.sap.mcp/sap-mcp
Provides an MCP gateway connecting SAP-related tools with Solana, DeFi, decentralized identity, and x402 payments.
TheProtocol — Sovereign AI Agent Platform
cloud.theprotocol/registry
Manages sovereign AI agents, identities, contracts, payments, governance, exchanges, and cross-frame token transfers.
AIMEAT
io.aimeat/aimeat
Provides a self-hosted agent operating system with agent work delegation, access controls, federation, hooks, SSO, security admin…
hyperion
com.thetempleofdoom.hyperion/hyperion
Acts as a paid MCP tool marketplace and utility gateway with server discovery, HTTP and JavaScript tools, research, data conversi…
GPT55 Model Gateway
xyz.558686.gpt55/token-gateway
Acts as a remote model gateway exposing GPT chat, coding and review services, lightweight text utilities, and prepaid or x402-bas…
Rokha
ai.rokha/rokha
Provides access to an agent-skill and MCP server registry, skill inspection and composition tools, OAuth connections, and agent a…
Japan Public Ledgers MCP
com.mcp-revenue-empire/japan-public-ledgers
Provides agent identity, memory, audit, trust, proxy, temporary email, webhook, CAPTCHA, and alerting capabilities alongside publ…