A Model Context Protocol server that can store and retrieve memories for LLM context control
A Model Context Protocol server that can store and retrieve memories for LLM context control. The mem0 mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 4 defined tools rather than through you.
A Model Context Protocol (MCP) server that integrates with Mem0.ai to provide persistent memory capabilities for LLMs. It allows AI agents to store and retrieve information across sessions.
Everything the assistant can do here goes through one of these:
Inputs — ** content (string) or messages (array of role/content objects), userId (string), runId / sessionId (string), agentId (string), appId (string)Behavior — ** Cloud V3 additions are asynchronous. By default, this tool polls the background queue until completed. Pass waitForCompletion: false to get theRequires — A Mem0 API keySelf-contained — All data stays on your machineYou will need 8 environment variables: MEM0_API_KEY, DEFAULT_USER_ID, DEFAULT_AGENT_ID, DEFAULT_APP_ID, SUPABASE_URL, SUPABASE_KEY, OPENAI_API_KEY, ORG_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This server supports three storage modes: 1. Cloud Storage Mode ☁️ (Recommended for production) * Requires a Mem0 API key (provided as MEM0_API_KEY environment variable) * Memories are persistently stored on Mem0's cloud servers * No local database needed * Full feature support with advanced filtering and search 2. Supabase Storage Mode 🗄️ (Recommended for self-hosting) * Requires
Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Plenty of AI and media services servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Mem0 MCP's toolset — Inputs, Behavior, Requires and 1 more — is a fair guide to whether it matches your workflow. It is maintained by pinkpixel-dev; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Inputs | ** content (string) or messages (array of role/content objects), userId (string), runId / sessionId (string), agentId (string), appId (string), metadata (object), infer (boolean), customInstructions (string), waitForComp |
| Behavior | ** Cloud V3 additions are asynchronous. By default, this tool polls the background queue until completed. Pass waitForCompletion: false to get the eventId immediately. |
| Requires | A Mem0 API key |
| Self-contained | All data stays on your machine |
{
"mcpServers": {
"mem0-mcp": {
"command": "npx",
"args": [
"-y",
"@pinkpixel/mem0-mcp"
],
"env": {
"MEM0_API_KEY": "YOUR_MEM0_API_KEY_HERE",
"DEFAULT_USER_ID": "user123",
"ORG_ID": "your-org-id",
"PROJECT_ID": "your-project-id"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
This server supports three storage modes: 1. Cloud Storage Mode ☁️ (Recommended for production) * Requires a Mem0 API key (provided as MEM0_API_KEY environment variable) * Memories are persistently stored on Mem0's cloud servers * No local database needed * Full feature support with advanced filtering and search 2. Supabase Storage Mode 🗄️ (Recommended for self-hosting) * Requires
| Variable | Description | Required |
|---|---|---|
| MEM0_API_KEY | Credential the server authenticates with. | Yes |
| DEFAULT_USER_ID | Configuration value read at startup. | Optional |
| DEFAULT_AGENT_ID | Configuration value read at startup. | Optional |
| DEFAULT_APP_ID | Configuration value read at startup. | Optional |
| SUPABASE_URL | Endpoint or connection string the server talks to. | Yes |
| SUPABASE_KEY | Credential the server authenticates with. | Yes |
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
| ORG_ID | Configuration value read at startup. | Optional |
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Give your assistant a voice — text-to-speech, voice cloning and audio tools from the ElevenLabs API.
Give your assistant a real code sandbox — isolated cloud VMs for actually running the code it writes.
The ML hub in your context window — search models, datasets, papers and run Spaces from the official server.