Mem0 MCP Server

by mem0ai Your server? Claim it

answering

Mem0 is answering right now. Last checked moments ago.

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

Uptime history 47 days of history · worst day 99%

47 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

597 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Mem0 missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mem0 --transport http https://mcp.mem0.ai/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mem0": {
      "url": "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

{
  "mcpServers": {
    "mem0": {
      "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

URL	Transport	State	Latency	Checked
https://mcp.mem0.ai/mcp	streamable-http	sign-in	789 ms	0 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.

517 installs/wk local only

memsprout

by memsprout

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

answering

Memstack

by isiomac

MCP server for persistent, searchable memory for AI agents.

39 installs/wk local only

Zdravo Cursor

by zdravo-ai

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

36 installs/wk local only

Goldhold

by jerrysrodz

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

30 installs/wk answering

Vibo Memory

by vnbochkarev-netizen

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

255 installs/wk local only

Cairn

by jasondostal

Persistent memory for AI agents and humans. Store, search, and discover patterns.

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 597 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 with the file path 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 597 ms on average, which is faster than 21% 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.