Cline

One-line config

Cline runs inside VS Code and reads MCP servers from its own settings file.

Config

sigil register --print

Add the inner sigil object to cline_mcp_settings.json in your VS Code user directory:

Platform	Path
macOS	~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Linux	~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

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

You can also add it from Cline’s MCP Servers panel, which edits the same file.

Use the path register --print outputs — it’s the stable shim, which survives Node version switches and reinstalls.

Make it get used

Cline reads Custom Instructions from its settings. Add:

You have access to Sigil, a persistent memory shared with every other AI
agent on this machine. Call `prime` at the start of a task. Before answering
questions about this project, past decisions, or the user's preferences,
call `search`. When the user shares a preference, decision, or constraint,
call `remember` with a short self-contained statement. Pass `cwd` so facts
attach to the right project.

Verify

Open the MCP Servers panel — sigil should be listed as connected with thirteen tools. Then:

sigil doctor --deep

Cline’s plan/act split

Cline’s Plan mode is a good place for search and its Act mode a good place for remember. Worth encoding in your instructions:

In Plan mode, call `search` to check what is already known before proposing
an approach. In Act mode, call `remember` when a decision gets made.

Troubleshooting

The server won’t connect. Check the JSON is valid, then reload the VS Code window.

It connected but errors. Stale shim path:

sigil connect

Tools are available but unused. Strengthen the custom instructions. This is the usual cause.