cognee-grok-bot plugin. The plugin connects that server and adds a skill that tells the bot to recall before it answers and to remember durable facts. Grok Bot signs you in with your Cognee account, so there is no API key to paste and nothing to install.
How it works
The plugin has two parts:
Grok Bot runs in the cloud and does not run plugin hooks, so unlike the Claude Code plugin nothing captures or recalls memory automatically. The skill steers the bot to call the tools itself. Its description asks the bot to load it at the start of every conversation and before any Cognee tool call.
A plugin cannot switch off Grok Bot’s own memory. If your Grok Bot has a built-in memory setting, turn it off so the two do not disagree.
Before you start
You need a Cognee Cloud account with a workspace. The hosted MCP server acts on the workspace your account belongs to. See which workspace a connection uses.1. Connect Cognee
Grok Bot uses the plugins on your Cursor account, so you add this one through the Cursor app. It is not in the public Cursor marketplace yet; you add thecognee-integrations repository as a marketplace yourself, or set up its two parts in a Grok Bot chat. This works on a free personal account.
- Install the plugin (recommended)
- Without the plugin: set it up in chat
- Link GitHub to your Cursor account first: open the Cursor dashboard, go to Integrations, and choose Connect next to GitHub. Without the link, Cursor’s requests to GitHub get rate-limited and the plugin can disappear from the marketplace shortly after it shows up.
-
In the Cursor app, open Customize in the sidebar and add this repository as a marketplace:
-
Install Cognee Memory for Grok Bot (
cognee-grok-bot) from that marketplace. The description ends with the plugin’s version. - In Grok Bot, open Connect apps → Your plugins and check that the plugin is listed.
-
In a new conversation, ask the bot to test the connection, so it loads the skill and uses Cognee once:
If you have not signed in yet, the bot shows a connect card: sign in with your Cognee account and click Allow Access. Ingestion takes about a minute. The answer should end with a
🧠 Saved to Cognee (cognee_test)line and a🧠 Cognee memory (cognee_test)line. Clean up withForget the dataset "cognee_test"; the bot asks you to confirm first.
@ and attach cognee (or the plugin) to the task if the bot does not pick it up on its own.
2. Pick a dataset
Every memory lives in a named dataset. The skill tells the bot to use one dataset per conversation and to pass it on every call. If you have not named one, the bot asks once and suggests a short name such aslondon_community. A team that wants shared memory agrees on one dataset name.
What Cognee did, after each answer
When an answer used recalled memory, or the bot saved something, it ends with one line per action:recall returned, not what the bot knows from the conversation. Unlike the Claude Code plugin’s credit line it has no [m1] tags, because those come from a recall hook and Grok Bot runs no hooks.
Tools
remember runs the full ingestion pipeline: about a minute for a short note, longer for large text or files. The skill has the bot poll check_ingestion_status until it reports DATASET_PROCESSING_COMPLETED before relying on the new memory.
forget deletes permanently. The skill tells the bot never to call it without your explicit confirmation of exactly what will be deleted, and to ask a second time, naming every dataset, before deleting everything.
Access
The hosted server acts as the signed-in user, with access to all of that user’s datasets. To give a bot narrower access, runcognee-mcp yourself in API mode with an API key that has only the permissions you want, and connect Grok Bot to that instead.
Try it
check_ingestion_status reports DATASET_PROCESSING_COMPLETED, then in a new chat:
🧠 Cognee memory (hackathon_test) line. Clean up with Forget the dataset "hackathon_test".