Cursor

Install and activate first — Getting started covers both. Without a key the wiring below succeeds and the server refuses with E_NO_KEY the moment your editor starts it.

kscope init wires Cursor when ~/.cursor exists. Cursor gets a rule file and no skill.

Wire it

cd ~/your-project
kscope init

Restart Cursor, then ask it to search your memory.

What init writes

What	Where
MCP entry	.cursor/mcp.json in the project, under mcpServers as kaleidoscope
Instructions	.cursor/rules/kaleidoscope.mdc
Skill	none
Receipt	.cursor/mcp.json.kaleidoscope-owner.json, and .cursor/rules/kaleidoscope.mdc.kaleidoscope-instruction-owner.json
Backup	.cursor/mcp.json.kaleidoscope-backup, when the file was already there

{
  "mcpServers": {
    "kaleidoscope": {
      "command": "/absolute/path/to/kscope",
      "args": ["mcp", "--profile", "your-project"]
    }
  }
}

Cursor’s entry carries no type field.

your-project is the profile init creates for the project, named after its folder. With an npm install, the command is ~/.kaleidoscope/bin/kscope, a copy of kscope that updates itself when you update kscope.

A project set up by an earlier version keeps its entry in ~/.cursor/mcp.json and the default profile. kscope init says so, and names the command that gives the project its own vault.

.cursor/mcp.json names this machine’s kscope, so init adds it to the project’s .gitignore, with its receipt and backup.

The rule instead of a skill

Cursor has no skill directory, so the rule file carries the instructions. Its frontmatter sets alwaysApply: true, and Cursor reads it every turn.

---
description: Apply Kaleidoscope memory policy safely
alwaysApply: true
---

If Cursor lists the tools but never calls them, check that file first. Give your agent the skill has the text it should hold.

Check it

kscope profile list
kscope profile launch your-project

launch prints the arguments and the tool list — search and remember — that the entry in .cursor/mcp.json should match. Its command is the kscope you ran, which is not the copy the entry names after an npm install.

Remove it

Delete each of these, and the receipt beside it:

• the kaleidoscope entry under mcpServers in .cursor/mcp.json
• .cursor/rules/kaleidoscope.mdc

Either one can go without the other. Your memory stays. Connect an editor or agent covers every editor at once.