Before any app: two things, once

01

Make an app key in your vault

Open your vault, go to Apps, choose Connect an app, name it and tick the folders it may read. The app key is shown once; copy it. Each app gets its own key, so you can revoke one without touching the others.

An app key, shown once
sigil_app.<app id>.<secret>
02

Have the connector on your computer

Nothing to install: your AI app starts it with npx -y sigil-connector. It needs Node.js 20 or newer.

01 / 07

Claude Desktop

Starts the connector itselfIn the vault: Claude Desktop
  1. In Claude Desktop open Settings, Developer, Edit Config.
  2. That opens claude_desktop_config.json. On macOS it lives in ~/Library/Application Support/Claude, on Windows in %APPDATA%\Claude.
  3. Add Sigil under mcpServers, next to any servers already there, and save.
  4. Quit Claude Desktop fully and open it again.
claude_desktop_config.json
{
  "mcpServers": {
    "sigil": {
      "command": "npx",
      "args": [
        "-y",
        "sigil-connector"
      ],
      "env": {
        "SIGIL_APP_KEY": "sigil_app.<app id>.<secret>",
        "SIGIL_URL": "https://sigilvault.fun"
      }
    }
  }
}

Sigil appears in the tools menu of a new chat. Claude asks before it uses a tool for the first time.

02 / 07

Claude Code

Starts the connector itselfIn the vault: Other
  1. Run the command below once in a terminal. It adds Sigil for every project of yours.
  2. To share it with one project only, put the same mcpServers block as for Claude Desktop in a file called .mcp.json in the project folder instead. Keep that file out of version control: it holds your app key.
  3. Start Claude Code and type /mcp to see that sigil is connected.
Terminal
claude mcp add sigil --scope user \
  --env SIGIL_APP_KEY=sigil_app.<app id>.<secret> \
  --env SIGIL_URL=https://sigilvault.fun \
  -- npx -y sigil-connector

Claude Code can now search and read the folders you shared, in any session.

03 / 07

Cursor

Starts the connector itselfIn the vault: Cursor
  1. For every project, open or create ~/.cursor/mcp.json. For one project only, use .cursor/mcp.json in the project folder.
  2. Add Sigil under mcpServers and save.
  3. Open Cursor Settings, MCP, and check that sigil shows as enabled.
~/.cursor/mcp.json
{
  "mcpServers": {
    "sigil": {
      "command": "npx",
      "args": [
        "-y",
        "sigil-connector"
      ],
      "env": {
        "SIGIL_APP_KEY": "sigil_app.<app id>.<secret>",
        "SIGIL_URL": "https://sigilvault.fun"
      }
    }
  }
}

Ask the agent something your notes can answer. It calls search_memories, then read_memory.

04 / 07

Windsurf

Starts the connector itselfIn the vault: Other
  1. Open ~/.codeium/windsurf/mcp_config.json, or reach it from the MCP section of Windsurf's settings.
  2. Add Sigil under mcpServers and save.
  3. Refresh the MCP servers in Windsurf's settings so it picks up the change.
mcp_config.json
{
  "mcpServers": {
    "sigil": {
      "command": "npx",
      "args": [
        "-y",
        "sigil-connector"
      ],
      "env": {
        "SIGIL_APP_KEY": "sigil_app.<app id>.<secret>",
        "SIGIL_URL": "https://sigilvault.fun"
      }
    }
  }
}

Cascade lists the three Sigil tools and uses them when your own notes can help.

05 / 07

VS Code

Starts the connector itselfIn the vault: Other
  1. Create .vscode/mcp.json in your project. VS Code lists servers under servers, not mcpServers.
  2. Save, then press Start above the server in that file.
  3. Open chat in agent mode and check that the Sigil tools are ticked in the tools list.
  4. Extensions that bring their own MCP settings, such as Cline, take the mcpServers block shown for Claude Desktop in their own settings file.
.vscode/mcp.json
{
  "servers": {
    "sigil": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "sigil-connector"
      ],
      "env": {
        "SIGIL_APP_KEY": "sigil_app.<app id>.<secret>",
        "SIGIL_URL": "https://sigilvault.fun"
      }
    }
  }
}

Keep the file out of version control, or move the key to an input variable: it holds your app key.

06 / 07

ChatGPT

Connects to an address you runIn the vault: ChatGPT
  1. ChatGPT reaches MCP servers over the internet, so the connector runs in HTTP mode on your computer. Start it with a long random token of your own.
  2. It listens on http://127.0.0.1:8787/mcp/<token>. Expose that port with an HTTPS tunnel service of your choice.
  3. In ChatGPT, turn on developer mode for connectors and add a custom connector with the tunnel address ending in /mcp/<token>, with no authentication. Which plans offer custom connectors is up to ChatGPT.
  4. Keep the address private. The token in the path is what keeps others out. Stop the connector, or revoke the app key, whenever access should end.
Terminal
SIGIL_APP_KEY=sigil_app.<app id>.<secret> \
SIGIL_URL=https://sigilvault.fun \
SIGIL_HTTP_TOKEN=<a long random string> \
npx -y sigil-connector --http --port 8787

Text that ChatGPT reads is processed on its servers under its own terms.

07 / 07

Any MCP client

Stdio or HTTPIn the vault: Other
  1. Any app that can start a local MCP server over stdio uses the command below with the two environment variables.
  2. Apps that only take a URL use HTTP mode, as described for ChatGPT.
  3. The connector offers four tools that read (get_profile, list_folders, search_memories and read_memory) and propose_memory, which suggests a memory to your inbox when you allow it.
Terminal
SIGIL_APP_KEY=sigil_app.<app id>.<secret> \
SIGIL_URL=https://sigilvault.fun \
npx -y sigil-connector

If the client speaks MCP, it can read your vault, and every read lands in your log.

After it is connected

Ask as usual

Ask something your notes can answer. The app searches titles, tags and first lines, then reads what looks relevant.

Watch the read log

Every request shows up in your vault under Read log: which app, what it saw and when.

Change your mind

Add or remove folders for an app at any time, or revoke it. A revoked key fails on its very next request.