Cursor
Install Nowledge Mem locally in Cursor today, then add Marketplace later if it becomes available to your account.
Recommended today: local plugin install
The most reliable path today is local install from ~/.cursor/plugins/local/nowledge-mem-cursor. It works before Marketplace acceptance and uses the same package you would later publish.
Marketplace is optional later
If Nowledge Mem eventually becomes visible in Cursor Marketplace for your account, you can switch to that path later. The local package path below is the user-ready path now.
The practical benefit is simple: install once, start a new agent session, and Cursor gets the rule, skills, hook, and MCP wiring together.
Before You Start
- Nowledge Mem running locally (installation) or a reachable remote Mem server
- Cursor IDE installed
- Recommended:
nmemin yourPATHif you want automatic Working Memory bootstrap and resumable handoff creation through the terminal tool
If Nowledge Mem is already running on the same machine through the desktop app, the easiest path is Settings -> Preferences -> Developer Tools -> Install CLI. That gives Cursor access to nmem for session-start Working Memory bootstrap and explicit handoff creation.
One-Minute Setup
Clone or open the package folder
git clone https://github.com/nowledge-co/community.git
cd communityCopy the plugin into Cursor's local plugin folder
mkdir -p ~/.cursor/plugins/local
rm -rf ~/.cursor/plugins/local/nowledge-mem-cursor
cp -R nowledge-mem-cursor-plugin ~/.cursor/plugins/local/nowledge-mem-cursorIf you want faster local iteration, you can try a symlink instead:
ln -s "$(pwd)/nowledge-mem-cursor-plugin" ~/.cursor/plugins/local/nowledge-mem-cursorCursor staff have confirmed that local plugin symlink resolution is currently buggy in practice, so copy-first is the reliable path.
Reload Cursor
Restart Cursor or run Developer: Reload Window.
If Cursor still shows Claude Code wording, save-thread, or hooks like beforeSubmitPrompt and stop, remove the older imported nowledge-mem package from Cursor first. The local package here should expose only sessionStart plus the four Nowledge Mem skills. The local plugin id is nowledge-mem-cursor specifically to avoid colliding with that imported package.
Start a new agent session
For the default same-machine setup, the bundled plugin assets are the intended zero-config path:
- plugin manifest
- rule
- skills
- session-start hook
- local
mcp.json
If nmem is installed, the session-start hook can preload Working Memory into the new Cursor session before the agent begins.
Configure MCP for remote Mem only
Only if you use remote Mem, open Settings (Cmd/Ctrl+Shift+J) -> Features -> Model Context Protocol and update the nowledge-mem server URL and headers.
If you also want the sessionStart hook and save-handoff skill to work against remote Mem, point the local nmem client at the same remote server:
nmem config client set url https://your-server:14242
nmem config client set api-key your-keyThe split is intentional:
- Cursor MCP settings drive the plugin's memory tools
nmem config client ...drives the terminal-side bootstrap and handoff flow on this machine
Update
If you installed through the local plugin folder:
- recommended copied path: replace
~/.cursor/plugins/local/nowledge-mem-cursorwith a fresh copy, then reload Cursor - optional symlink path: pull the latest
communitychanges and reload Cursor, but switch back to copied install if Cursor stops detecting the plugin
If Marketplace support appears later, you can uninstall the local copy and move to Marketplace.
Customize Safely
Use Cursor's own rule files for behavior changes:
.cursor/rules/*.mdc.cursorrules
Keep the packaged Nowledge Mem rule as the default. Do not patch the installed plugin files under ~/.cursor/plugins/.... Full map: Customize Integration Behavior.
Your First Success State
You know the plugin is set up correctly when:
- the plugin is installed from
~/.cursor/plugins/local/nowledge-mem-cursor - you start a new Cursor agent session
- if
nmemis installed, Working Memory is already available at the start of the session - same-machine setup works without hand-editing MCP config
- in remote mode, updating the
nowledge-memMCP server is enough to restore the same behavior - Cursor is not showing a stale Claude-oriented package surface such as
save-thread,beforeSubmitPrompt, orstop
What You Get
- Bundled
.cursor-plugin/plugin.json - Bundled
hooks/hooks.jsonwith asessionStartWorking Memory bootstrap - Bundled
mcp.jsonfor local Nowledge Mem MCP connectivity - An always-on rule for Working Memory, routed recall, distillation, and handoff semantics
- Four skills:
read-working-memory,search-memory,distill-memory, andsave-handoff
What Users Usually Care About
For a fresh install, the important answers are simple:
- local Mem: install the plugin and start a new session
- remote Mem: install the plugin, then update the
nowledge-memMCP server URL and headers; if you want bootstrap and handoff too, also pointnmemat the same remote server - best Cursor experience: keep
nmeminstalled so the session-start hook can preload Working Memory and Cursor can create handoff summaries when needed
Important Constraint
This package intentionally does not expose save-thread.
Nowledge Mem does not yet have a first-class live Cursor session importer here, so summary-only behavior must stay named save-handoff, not save-thread. That keeps the behavior clear today and leaves room for a future real thread-save path when the runtime support exists.
Package Shape
This package is already arranged in Cursor's plugin format:
.cursor-plugin/plugin.json
rules/nowledge-mem.mdc
skills/*/SKILL.md
hooks/hooks.json
hooks/session-start.mjs
mcp.jsonCursor's local plugin folder expects .cursor-plugin/plugin.json at the package root. This package already matches that contract, so the local install path above is stable and direct.
Marketplace Later
If Cursor Marketplace accepts the package later, install Nowledge Mem there and keep the same behavior. Until then, the local plugin folder is the right path for users.