MCP server
One memory, every agent.
The cognee MCP server gives Claude Code, Cursor, and any MCP client shared graph memory — built from your documents and data, available in every session.
Get running
Start the server with Docker, then connect your client. The HTTP endpoint serves every MCP client at once.
$ echo "LLM_API_KEY=your_api_key_here" > .env
$ docker run -e TRANSPORT_MODE=http --env-file ./.env -p 8000:8000 --rm -it cognee/cognee-mcp:main
# HTTP transport (server from the Docker step)
$ claude mcp add --transport http cognee http://localhost:8000/mcp -s project
# Or run locally over stdio
$ claude mcp add cognee -s project -e LLM_API_KEY="your-key" -- uv --directory /path/to/cognee-mcp run cognee-mcp
# Point your client at the HTTP endpoint
http://localhost:8000/mcp
Cursor, Claude Desktop, Continue, Cline, and Roo Code all connect to the same endpoint — see the per-client guides for setup details.
What your agent gets
Persistent project memory
Context survives across sessions. Your agent picks up tomorrow where it left off today, instead of starting from zero.
Graph search over your data
Cognee builds a knowledge graph from your documents and data, so agents retrieve connected facts — not just similar text.
One memory, shared everywhere
Claude Code, Cursor, and every other MCP client you use read and write the same memory. Switch tools without losing context.