Cursor

Auto-wired

Setup detects Cursor and writes Sigil’s entry into ~/.cursor/mcp.json. Cursor then has the same brain as Claude Code — thirteen MCP tools against the same memory.

Setup

sigil init          # or the browser wizard
sigil doctor        # verify

Then Cursor → Settings → MCP and confirm sigil is in the server list.

Manual config

sigil register --print

{
  "mcpServers": {
    "sigil": {
      "command": "/Users/you/.sigil/bin/sigil-mcp",
      "args": []
    }
  }
}

Add the inner sigil object to ~/.cursor/mcp.json. Use the output of register --print rather than the example — it has the correct paths for your machine.

Or use HTTP

sigil register --http registers the daemon’s HTTP transport instead. The URL never changes, which makes it the most durable option across reinstalls.

Make Cursor use it

Cursor has no hook layer — it calls tools when it decides to. Without a nudge, it usually doesn’t.

Add this to your Cursor rules (Settings → Rules for AI, or .cursor/rules):

You have access to a persistent memory system called Sigil.

- Call `prime` at the start of every session to load standing context.
- Before answering questions about this project, past decisions, or my
  preferences, call `search`.
- When I share a preference, decision, or constraint, call `remember`
  with a short self-contained statement.
- Pass `cwd` on `search`, `remember`, and `ingest` so facts attach to
  this project's pod.

The cwd line matters more than it looks — it’s what scopes memory to this repo instead of dumping everything into one undifferentiated pile.

The tools you’ll actually see used

Tool
prime	Session start — loads hot context
search	Hybrid search over facts
search_entity	Look up a person, project, or service by name
remember	Save atomic facts
ingest	Store a document whole
list_documents / get_document	Find and read stored documents
status	Knowledge base statistics

Full reference: MCP tools.

Capture

Two paths, since there are no hooks:

The agent decides. With the rules above, Cursor calls remember when you share something worth keeping.

You decide. From any terminal:

sigil remember "Cursor's composer struggles with this monorepo's path aliases"

Either way it’s the same brain — Claude Code will see it on your next prompt there.

Troubleshooting

sigil doesn’t appear in Cursor’s MCP list. Restart Cursor after registering; it reads mcp.json at startup.

It appears but errors. The shim path is stale:

sigil connect --clients cursor
sigil doctor --deep

It works but Cursor never calls it. That’s a prompting problem. Strengthen the rules above — particularly the “before answering” instruction, which is what converts memory from available to used.