Skip to main content
Give your agents persistent memory backed by your Cognee Cloud tenant. Once connected, an agent recalls relevant context before it answers and writes new knowledge back into your knowledge graph automatically — memory survives across sessions, terminals, and even across different agents that share a dataset. This section walks through connecting each supported agent to Cognee Cloud. For local-only setups and full configuration references, each page links out to the dedicated integration guide.

​
How agents connect

Agents read and write Cognee memory in one of a few ways. Pick the one your agent supports:

​
Before you start

Every Cloud connection except the hosted MCP server needs two values from your tenant:
1

Copy your tenant base URL

Your Cloud base URL looks like https://your-tenant.aws.cognee.ai. It’s shown in the dashboard and in the Integrations page, which prefills it into every copy-on-click snippet.
2

Create an API key

Generate a key on the API Keys page. Store it securely — treat it like a password.
Most plugins read these from environment variables:
Sharing one COGNEE_API_KEY across several agents keeps working — Claude Code, Codex, and OpenCode installs that authenticate this way stay connected and are still recognized from the prefixes they put on their session IDs (cc_, codex_, opencode_), until that plugin gets an identity of its own. Alternatively, supported plugins (claude-code, desktop, codex, opencode, openclaw, mcp, api) can be given their own agent identity and their own labeled key, so each one can be tracked and revoked separately. See per-plugin agent identities.
The in-product Integrations page (under CONNECT in the sidebar) has quickstart cards for each agent that inject your live base URL and API key into ready-to-paste snippets — the fastest path to a working connection.

​
Choose your agent

Claude Code

Install the memory plugin and point it at your tenant — memory across every session.

Codex

Enable hooks, install the plugin, and connect to Cloud. Shares a dataset with Claude Code.

Cursor

Register Cognee as an MCP tool provider in Cursor’s Agent.

VS Code (Cognee extension)

A citable project memory extension — remember, ask, and recall in-editor.

Claude Desktop

Add Cognee as an MCP server in Claude Desktop’s config.

OpenClaw

Register Cognee as OpenClaw’s memory provider pointed at your Cloud tenant, with multi-scope recall.

Hermes Agent

Drop-in memory provider in remote mode — turns are captured and promoted to the graph.

Grok Bot

Install the plugin and sign in with your Cognee account — hosted MCP plus a memory skill.
Don’t see your agent? Any framework can connect through the SDK, an MCP server, or the REST API — see Connecting an Agent and the full integration catalog.