Skip to main content
Cursor is an AI-powered code editor with native support for the Model Context Protocol. Register Cognee as an MCP tool provider and Cursor’s Agent can remember, recall, and forget against your Cognee Cloud tenant.

​
1. Add Cognee to your MCP config

Cursor reads MCP servers from ~/.cursor/mcp.json. Add a cognee entry that points at your tenant, using your API Base URL and a key from the API Keys page:
This is the stdio form the in-product Integrations page generates. Cognee runs via uvx (requires uv) — no separate install of Cognee itself. You can also open the config from Settings → Tools & MCP → + Add MCP Server.
uvx requires uv to be installed first — it is not bundled with Cursor or Windows. A 'uvx' is not recognized... error in the MCP logs means uv isn’t on PATH.
  • macOS/Linux: curl -LsSf https://astral.sh/uv/install.sh | sh
  • Windows (PowerShell): powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
Restart your terminal (and fully restart Cursor) after installing so the updated PATH takes effect.
If you already use other MCP servers in Cursor, merge the cognee entry into your existing mcpServers block instead of replacing the file.

​
2. Verify

In Settings → Tools & MCP, restart Cursor (or use the toggle to refresh the connection). You should see Cognee’s tools (remember, recall, forget) listed, confirming the server is connected.

​
3. Use it

  1. Open the Chat panel and make sure Agent mode is selected.
  2. Issue prompts that use Cognee tools:
    • “Remember this file in Cognee”
    • “Recall authentication logic from Cognee”
    • “What do you know from cognee?”
Prefer a dedicated in-editor memory UI with citations? Cursor is built on VS Code, so the Cognee VS Code extension also runs in Cursor.

Full MCP guide

Local and Docker transports, and troubleshooting

Cloud MCP

How MCP clients connect to Cognee Cloud

Sessions

Inspect what Cursor stored in your live Sessions