Mem0 (BYOK)

Mem0 (BYOK) — connector documentation

• MCP endpoint: https://byok-mem0.connectorbay.com/mcp
• REST API: POST https://byok-mem0.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-mem0.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Mem0 API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-mem0.connectorbay.com/health · Tool schemas: https://byok-mem0.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-mem0 · agent@connectorbay.com

What Mem0 (BYOK) is for

Mem0 (BYOK) lets an AI assistant read your own Mem0 data through the Mem0 API with a key you supply (API key). Read-only: 9 tools (check_key, list_memories, get_memory, get_memory_history, list_entities, list_events, get_stats, list_organizations, list_projects). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.mem0.ai. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Mem0. Mem0 and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Is my Mem0 API key valid and which project is it for?"
• "What does Mem0 remember about user alice?"
• "Show one Mem0 memory by its ID"
• "How did this Mem0 memory change over time?"
• "Which users and agents does my Mem0 project know about?"
• "Did any Mem0 memory operations fail recently?"

What it does

• check_key: Check the API key and show the organization, project and account email it resolves to.
• list_memories: List stored memories of one user, agent, app or run, with the memory text, categories, metadata and timestamps; page with page and page_size. At least one of user_id, agent_id, app_id or run_id is needed.
• get_memory: Get one memory by ID with its text, owner, categories, metadata, expiry and timestamps.
• get_memory_history: Show the change history of one memory: each add, update or delete with old and new text and time.
• list_entities: List the users, agents, apps and runs that have memories in the project, with counts of each type.
• list_events: List recent memory operation events (adds, searches and so on) with type, status, latency and timing; useful to find failed operations.
• get_stats: Show usage statistics: total memories, add and retrieval events and users, agents and runs with memories.
• list_organizations: List the organizations the key's user belongs to with plan, role and default flag.
• list_projects: List the projects of one organization with description, memory settings, graph flag and timestamps.

BYOK key

You bring your own Mem0 API key (https://app.mem0.ai/dashboard/api-keys). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.mem0.ai over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Notices

Read-only: this connector lists and reads stored memories. It never adds, updates, deletes or semantically searches memories. Memories may contain personal data.

Data sources

• https://docs.mem0.ai/api-reference (the API this connector calls, with a BYOK key)

Live from the Mem0 API (api.mem0.ai) with a BYOK key; documentation: https://docs.mem0.ai/api-reference. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Mem0. Mem0 and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Mem0 account.

Built for: Worldwide. Languages: English.

Mem0 (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Mem0 (BYOK) is. Mem0 (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Mem0 data: Read your Mem0 platform memories, memory history, users and agents, events, usage statistics, organizations and projects with your own API key. You bring your own Mem0 API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Mem0 call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.mem0.ai, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Mem0 rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Mem0 receives. The request we make on your behalf, including the key and the arguments, under Mem0's own terms and privacy policy. Mem0 acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Mem0 gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Mem0 data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Mem0 (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Mem0 at any time to end all access.

Children. Mem0 (BYOK) is a general-audience service operated by the adult using the assistant, under Mem0's own age rules.

Changes. We will post changes here with a new effective date.

Mem0 (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Mem0 (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Mem0 (BYOK) provides: Read your Mem0 platform memories, memory history, users and agents, events, usage statistics, organizations and projects with your own API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Mem0 credentials and only access data you are allowed to access. Mem0's terms apply to your use of Mem0; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Mem0. Mem0 and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Mem0 returns, lightly trimmed; it may be incomplete, delayed or changed by Mem0. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Mem0 account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Mem0's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Mem0 may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Mem0 key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Mem0 takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-mem0

Mem0 (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-mem0.connectorbay.com/mcp
• REST API: https://byok-mem0.connectorbay.com/openapi.json
• Live status: https://byok-mem0.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Mem0 (BYOK) never asks for them.