Mem0 documents an official cloud-hosted Model Context Protocol server at docs.mem0.ai/platform/mem0-mcp, exposed over Streamable HTTP at `https://mcp.mem0.ai/mcp` with no local install required. Setup uses `npx mcp-add --name mem0-mcp --type http --url https://mcp.mem0.ai/mcp` for Claude, Claude Code, Cursor, Windsurf, VS Code, and OpenCode per Mem0 docs. Tools include `add_memory`, `search_memories`, `get_memories`, `get_memory`, `update_memory`, `delete_memory`, `delete_all_memories`, `delete_entities`, `list_entities`, `list_events`, and `get_event_status`. Authentication uses a Mem0 Platform API key (`MEM0_API_KEY`); the legacy mem0ai/mem0-mcp GitHub repo is archived in favor of this hosted server.
Use cases
- Let Cursor agents autonomously save and search user preferences across sessions
- Add long-term memory to Claude Code without custom Mem0 SDK glue in every prompt
- Scope memories per user_id/agent_id with structured filters via MCP tools
- Track async memory operations with list_events and get_event_status
- Replace archived local mem0-mcp-server with Mem0's managed HTTP endpoint
Key features
- Claude Desktop
- Claude Code
- Cursor
- VS Code
- Codex
- Windsurf
- OpenCode
Frequently Asked Questions
- Is the mem0ai/mem0-mcp GitHub repo still maintained?
- No—Mem0 archived it and points users to the cloud MCP at mcp.mem0.ai.
- Do I need to run a local Python server?
- No—the official path is Mem0's hosted HTTP MCP; local uvx mem0-mcp-server is legacy.
- How many MCP tools are exposed?
- Mem0 docs list 11 tools covering add, search, get, update, delete, entities, and events.
Related
Related
3 Indexed items
Mem0 MCP Server
Mem0 documents a hosted Model Context Protocol server at https://mcp.mem0.ai/mcp that exposes Platform memory tools (`add_memory`, `search_memories`, `get_memories`, `update_memory`, `delete_memory`, `delete_all_memories`, `delete_entities`, `list_entities`, `list_events`, `get_event_status`) to Claude, Claude Code, Codex, Cursor, Windsurf, VS Code, and OpenCode. Setup uses `npx mcp-add` with HTTP transport or manual JSON/TOML client configs; Codex requires `MEM0_API_KEY` as bearer token per docs.mem0.ai/platform/mem0-mcp. The cloud server needs a Mem0 Platform API key from the dashboard and Node.js for the installer—no local vector database required for the hosted path.
Graphiti MCP Server
Zep documents an experimental Graphiti Model Context Protocol server at help.getzep.com/graphiti/getting-started/mcp-server, with AI client integration also referenced at `https://help.getzep.com/_mcp/server` per Zep docs. The open-source implementation lives in getzep/graphiti/mcp_server with HTTP transport at `/mcp/` (default localhost:8000) or stdio mode. Tools include `add_episode`, `search_facts`, `search_nodes`, `get_episodes`, `delete_episode`, `clear_graph`, and `get_status` per the Graphiti MCP README; newer README entries also list `add_memory`, `add_triplet`, `search_memory_facts`, `summarize_saga`, `build_communities`, and `get_episode_entities`. Graphiti is Zep's open-source temporal knowledge graph framework for Context Graphs with real-time incremental updates and hybrid retrieval.
PostHog MCP Server
PostHog documents a free hosted Model Context Protocol endpoint at `https://mcp.posthog.com/mcp` per posthog.com/docs/model-context-protocol that lets MCP clients query analytics, manage feature flags, investigate errors, run HogQL, triage support workflows, and configure CDP destinations from natural-language prompts. The PostHog Wizard installs the server into Cursor, Claude Code, Claude Desktop, Codex, VS Code, Windsurf, and Zed via `npx @posthog/wizard@latest mcp add`. Authentication routes to the correct US or EU data region; manual setups can pass a personal API key with the MCP Server preset through `mcp-remote` and an `Authorization` Bearer header. Source lives in the PostHog monorepo at `services/mcp` (the standalone PostHog/mcp repository redirects there).