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.
Use cases
- Give coding agents persistent user preferences across sessions via add_memory/search_memories
- Wire Claude Code or Cursor to Mem0 without self-hosting Qdrant stacks
- Bulk reset project-scoped memories with delete_all_memories during test harness teardown
- Audit async memory jobs through list_events and get_event_status
- Pair hosted MCP with Mem0 Platform quickstart for production agent memory
Key features
- Claude Desktop
- Claude Code
- Cursor
- Codex
- Windsurf
- VS Code
- OpenCode
Frequently Asked Questions
- Is this the self-hosted OpenMemory MCP?
- Docs distinguish hosted https://mcp.mem0.ai from self-hosted openmemory/api against your own Qdrant stack.
- What if connection fails?
- Mem0 troubleshooting lists invalid API key, missing Node.js for npx, or client misconfiguration.
- Can agents update memories?
- Yes—update_memory and delete_memory tools are documented alongside search and list operations.
Related
Related
3 Indexed items
Mem0 MCP Server
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.
Apify MCP Server
Apify documents an official Model Context Protocol server hosted at https://mcp.apify.com that speaks Streamable HTTP in line with the current MCP specification; Apify warns that SSE transport was deprecated for removal April 1, 2026. Hosted clients authenticate through browser OAuth or by supplying Bearer tokens sourced from Console → Settings → Integrations (`APIFY_TOKEN`), can pin tool bundles via URL query (`?tools=actors,docs,apify/rag-web-browser` style examples reproduce Apify wording), optionally append `telemetry-enabled=false`, and benefit from inferred structured-output schemas surfaced for Actor tooling on hosted endpoints unlike the default stdio server. When MCP clients refuse remote transports, docs recommend `npx -y @apify/actors-mcp-server` with `APIFY_TOKEN` for stdio, Node.js ≥18, and adherence to documented per-user throughput (Apify cites up to thirty requests per second across Actor runs plus storage/documentation calls). Specialized payment modes (open x402 on Base plus Skyfire) appear as optional adjunct pages inside the broader integration handbook.
Langfuse MCP Server
Langfuse documents two MCP surfaces: a hosted Prompt Management server at `https://cloud.langfuse.com/api/public/mcp` (streamable HTTP, built into the platform per langfuse.com/docs/prompt-management/features/mcp-server) with tools such as `createTextPrompt`, `createChatPrompt`, `getPrompt`, and `updatePromptLabels`; and a public Docs MCP at `https://langfuse.com/api/mcp` for semantic search over Langfuse documentation (`searchLangfuseDocs`) without authentication. The legacy `langfuse/mcp-server-langfuse` Node server remains for local command-based setups with LANGFUSE_PUBLIC_KEY and LANGFUSE_SECRET_KEY. Langfuse positions MCP for agentic onboarding—IDE agents can add tracing to OpenAI, Anthropic, or LangChain codebases from the Get Started agentic tab.