mcpbeat Sign in

Mem0 MCP Server

answering

Mem0 is answering right now. Last checked 2 min ago.

Persistent memory for AI agents: add, search, update, and delete long-term memories.

Uptime history 91 days of history · worst day 92%
91 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
894 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Mem0 every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add mem0 --transport http https://mcp.mem0.ai/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.mem0.ai/mcp
~/.codex/config.toml
[mcp_servers.mem0]
url = "https://mcp.mem0.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mem0": {
      "url": "https://mcp.mem0.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mem0": {
      "type": "http",
      "url": "https://mcp.mem0.ai/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.mem0.ai/mcp streamable-http sign-in 501 ms 2 min ago

Alternatives to Mem0

same job, measured the same way
Memory
by humaux

Persistent long-term memory for AI agents: semantic search, knowledge graph, and task canvas.

answering
Enquire MCP
by oomkapwn

Long-term memory for AI agents — your Obsidian vault as searchable persistent memory.

458 installs/wk local only
memsprout
by memsprout

shared AI-context layer for teams — persistent memory your agents search and update over MCP

answering
Membase
by membase

Long-term memory for you and your AIs: search memories, read the profile, add facts and documents.

answering
Memstack
by isiomac

MCP server for persistent, searchable memory for AI agents.

119 installs/wk local only
Zdravo Cursor
by zdravo-ai

Persistent AI memory for Cursor. Save and search memories via Zdravo.

35 installs/wk local only
Goldhold
by jerrysrodz

Persistent memory for AI agents. Search, store, and recall across sessions.

93 installs/wk answering
Vibo Memory
by vnbochkarev-netizen

Memory for AI agents: persistent L1/L2/L3, web-search savings, thread memory.

96 installs/wk local only

Mem0 — questions

Answers built from our own checks of this server.

Why is there no tool list for Mem0?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Mem0 working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 894 ms. The bar chart above shows every period we have measured.
How do I connect Mem0?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Mem0?
No API key is involved. Mem0 answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Mem0?
It answers our handshake in 894 ms on average, which is faster than 8% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.