Meko for Cursor
Cursor’s agent knows your repo, but not what you decided in the terminal last week. It cannot hand what it learned to the next person who opens the project.
Over MCP, Meko provides Cursor with:
Agent-scoped memory
What your agent learns persists beyond the session and is readable via every AI tool you connect to.
A shared knowledge base
Documents and promoted conclusions are searchable by all agents and teammates with access to the datapack.
A trace of every read and write
Each conversation is stored with its reasoning, so you can see what an agent did and why.
Your repo gets memory that lasts
Commit one config file and everyone who clones the project inherits what its agents already learned, in Cursor and in every other tool they connect. The installer sets up the server, the skill, and session hooks.
How Meko Benefits Cursor
Pick up where the repo left off
“What does Meko have on the caching layer from last sprint?”
Cursor searches the project’s memory before answering, so nobody has to re-explain the codebase.
Save the why behind a change
“Remember in Meko that we dropped the cache rewrite, and why.”
Stored with its reasoning, connected to the decisions it reached.
Continue another agent’s work
“Check Meko for what my Claude session found yesterday.”
Every write is tagged by an agent. A search returns all shared memories across the connected agents.
Onboard the next developer by cloning
The config is located at .cursor/mcp.json at the repo root. A new teammate clones, opens Cursor, and the project’s memory is already there.
Connecting Meko in Cursor
1. One command connects Cursor and teaches it when to use Meko:
npx @yugabytedb/meko-mcp --client cursor --api-key <your-api-key>The installer registers the Meko MCP server, installs the meko-mcp-tools agent skill that tells Cursor when to record and when to recall on its own, and wires Cursor’s session hooks.
2. Generate the API key in the Meko portal under Settings, then API Keys
In Cursor, ask the agent to save a conversation or remember a fact when you want it captured for certain. Claude Code adds fully automatic capture on top.
3. To share the connection with everyone who clones the repo, add the manual entry to .cursor/mcp.json at the project root and keep the API key in an environment variable.
Cursor performs best with a limited number of active tools across all servers. Older releases enforced a hard cap of roughly 40. Meko’s compact toolset leaves room for the rest of your stack.