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.
Use cases
- Let Cursor agents add episodes and search facts in a temporal knowledge graph
- Prototype Graph RAG with hybrid semantic/keyword/graph retrieval via MCP
- Manage entity communities and saga summaries for long-running agent workflows
- Self-host Graphiti MCP with Neo4j/FalkorDB backends per graphiti mcp_server docs
- Evaluate Zep Context Graph patterns before adopting Zep Cloud managed memory
Key features
- Claude Desktop
- Cursor
- VS Code
- Copilot
Frequently Asked Questions
- Is Graphiti MCP the same as Zep Cloud?
- Graphiti is Zep's open-source framework; Zep Cloud is the managed service at getzep.com with separate SDK APIs.
- Is the MCP server stable?
- Zep docs label Graphiti MCP as experimental; tool names evolved in recent README updates.
- What backend does it need?
- The mcp_server README documents Neo4j/FalkorDB configuration via config/config.yaml.
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.
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).
MotherDuck MCP Server
MotherDuck documents a remote Model Context Protocol server at motherduck.com/docs/sql-reference/mcp hosted at `https://api.motherduck.com/mcp` with OAuth (or Bearer token) and read-write SQL access to MotherDuck cloud databases. Tools include `list_databases`, `list_tables`, `list_columns`, `search_catalog`, `query`, `query_rw`, `ask_docs_question`, Dive tools (`list_dives`, `read_dive`, `view_dive`, `save_dive`, etc.), and Flight scheduling tools (`list_flights`, `create_flight`, `run_flight`, etc.) per MotherDuck MCP docs. For local DuckDB files or custom configs, MotherDuck points to the open-source `mcp-server-motherduck` package (`uvx mcp-server-motherduck --db-path md:`) on github.com/motherduckdb/mcp-server-motherduck.