Cursor
Cursor can remember you and your projects: your preferences, your team's decisions and the conventions of each project, kept across chats and machines. The Geniffy plugin does it by itself. The MCP server on its own gives Cursor's agent the memory tools, for when you ask.
The plugin
Install it
As a local plugin, from its public repository:
git clone https://github.com/Geniffy/geniffy-cursor ~/.cursor/plugins/local/geniffySign in
The first time Cursor uses Geniffy, it asks you to connect it (Cursor Settings, MCP): sign in and press
Allow. That gives the agent the memory tools. Then type geniffy login in a chat, once, for automatic
memory: your browser opens Geniffy again, and there is no key to copy. The plugin's hooks run with Node.js 18 or
later.
From then on:
- Each chat starts knowing you. The agent gets a short summary: what lasts about you, what is going on now, and what was said before about this project.
- What you discuss is saved as you go. When a turn ends, the exchange is saved in the background, with who said what, so your words become facts about you and the agent's do not.
- Secrets and code stay on your computer. Keys, tokens and passwords are removed before anything is saved, and code blocks are left out.
- Reading never asks; changing does. Searching your memory runs without a prompt. Saving, correcting and forgetting ask first.
| Type in a chat | What it does |
|---|---|
geniffy status |
Signed in or not, saving on or paused, and what was saved last |
geniffy pause, geniffy resume |
Stop or restart saving. Chats still start with what Geniffy remembers |
geniffy logout |
Sign out on this computer |
The plugin answers these itself: they never reach the model. It is open source: Geniffy/geniffy-cursor.
Only the memory tools
To give Cursor's agent the memory tools without the automatic recall and saving, add the MCP server on its own.
Add the server
Use the button, or put this in ~/.cursor/mcp.json for every project, or in .cursor/mcp.json at a
project's root for that project only:
{
"mcpServers": {
"geniffy": {
"url": "https://api.geniffy.com/mcp"
}
}
}Sign in
The first time Cursor uses Geniffy, it asks you to sign in. Sign in to Geniffy and press Allow. Cursor connects from your computer, so the approval screen names it as an app on this computer.
With an API key
Where signing in is not an option, send a Geniffy API key as a header instead:
{
"mcpServers": {
"geniffy": {
"url": "https://api.geniffy.com/mcp",
"headers": { "Authorization": "Bearer gnf_live_..." }
}
}
}A key is a secret: keep this file out of version control.