Install
Requires Node.js on your
PATH. Installing Cursor does not put one there.Authenticate
Open a new chat in Cursor and run:- macOS / Linux (zsh)
- macOS / Linux (bash)
- Windows (PowerShell)
/supermemory-status.
Prefer the terminal?
Prefer the terminal?
The slash commands just run the plugin’s CLI for you. To drive it yourself:
CURSOR_PLUGIN_ROOT is set for plugin hooks. If it is empty in your shell, run node dist/cli.js <command> from the installed plugin directory.Credentials are stored in ~/.supermemory-cursor/credentials.json.How It Works
Skills and Commands
MCP Tools
Every tool that takes a
container argument accepts:
"user"(default): personal memories for the current repository"project": project knowledge for the current repository"both": both scopes plus compatible legacy memories- any custom string: used as a raw container tag
user and project write to the same repository container. The sm_scope metadata field is what keeps personal and session memories separate from explicit project knowledge when an agent asks for one scope.
Container Tags
Cursor shares one repository tag with the Claude Code, OpenAI Codex, and OpenCode plugins, so agents working on the same repo read and write the same memory:cursor_user_* and cursor_project_* tags, along with legacy tags from the other agents. New writes only use the unified repository tag. Set repoContainerTag only when you need an explicit shared override.
Configuration
Environment variables
Global config
~/.config/cursor/supermemory.json holds user-wide defaults and applies to all projects.
Project config
.cursor/.supermemory/config.json holds per-workspace overrides and wins over global config. Add it to .gitignore if it contains an API key.
You can also set these from the agent with
supermemory_set_config, or edit the file by hand.
Log Out
Run/supermemory-logout in Cursor.
This removes the stored credentials. Your memories in Supermemory are preserved.
Next Steps
GitHub Repository
Source code, issues, and detailed README.