The Graphiti MCP Server is an experimental implementation that exposes Graphiti’s key functionality through the Model Context Protocol (MCP). This enables AI assistants like Claude Desktop, Cursor, and VS Code with Copilot to interact with Graphiti’s knowledge graph capabilities, providing persistent context and contextual awareness.
The Graphiti MCP Server bridges AI assistants with Graphiti’s temporally-aware knowledge graphs, allowing assistants to maintain persistent context across conversations and sessions. Unlike traditional RAG methods, it continuously integrates user interactions, structured and unstructured data, and external information into a coherent, queryable graph.
The MCP server exposes Graphiti’s core capabilities:
This quick start uses OpenAI and FalkorDB (default). The server supports multiple LLM providers (OpenAI, Anthropic, Gemini, Grogu, Azure OpenAI) and databases (FalkorDB, Neo4j). For detailed configuration options, see the MCP Server README.
Before getting started, ensure you have:
Configuration follows a precedence hierarchy: command-line arguments override environment variables, which override config.yaml settings.
Set up your environment variables in a .env file:
Start the MCP server:
For development with custom options:
The MCP server supports integration with multiple AI assistants through different transport protocols.
Configure Claude Desktop to connect via the stdio transport:
For Cursor, use the SSE transport configuration:
VS Code with Copilot can connect to the MCP server using HTTP endpoints. Configure your VS Code settings to point to the running MCP server.
Once connected, AI assistants have access to these Graphiti tools:
add_episode - Store episodes and interactions in the knowledge graphsearch_facts - Find relevant facts and relationshipssearch_nodes - Search for entity summaries and informationget_episodes - Retrieve recent episodes for contextdelete_episode - Remove episodes from the graphclear_graph - Reset the knowledge graph entirelyFor containerized deployment, use the provided Docker Compose setup:
This starts both the database (FalkorDB or Neo4j) and the MCP server with SSE transport enabled. Docker Compose can launch services in unified or separate containers with sensible defaults for immediate use.
Episode processing uses asynchronous queuing with concurrency controlled by SEMAPHORE_LIMIT. The MCP server README provides tier-specific guidelines for major LLM providers to prevent rate-limiting while maximizing throughput.
The framework includes optional anonymous telemetry collection that captures only system information. Telemetry never exposes API keys or graph content. Disable telemetry by setting:
For comprehensive configuration options, advanced features, and troubleshooting:
The MCP server is experimental and under active development. Features and APIs may change between releases.