Skip to main content
Cognee runs as an MCP (Model Context Protocol) server. Any MCP-compatible client (Claude Desktop, Cursor, VS Code Copilot) can connect to it as a tool provider. The MCP server can run locally or connect to your Cognee Cloud tenant.

Step 1 — Start the MCP server

Connect the MCP server to Cognee Cloud using your API Base URL and API key from the API Keys page:
For local mode (no Cloud connection), omit the --serve-url and --serve-api-key flags. The server will manage its own local knowledge graph. Local mode requires an LLM_API_KEY environment variable.

Step 2 — Add to your MCP client config

Add Cognee as a tool server in your MCP client’s configuration. For an SSE connection to a running server, point the client at the server URL:
Alternatively, you can run the server over stdio — the client launches cognee-mcp itself. Install it with pip install cognee-mcp, then use this config (this is the form the in-product Integrations page generates):
For per-client config file locations (Claude Desktop, Cursor, Hermes, VS Code, Gemini CLI, Cline), see Integrations.

Step 3 — Available tools

Once connected, your MCP client gets the Cognee API v1 memory tools: For detailed setup per client, see the MCP integration guides.

Next steps

Cloud SDK

Connect to Cognee Cloud programmatically using the Python SDK.

Cloud functionality

Explore the full API surface available in Cognee Cloud.