Sigil MCP Server

What the code does

We read the source, 13 min ago · rules 3dff92dd89df

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

      - name: Post / update PR comment
        env:
          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add sigil -- npx -y sigild

{
  "mcpServers": {
    "sigil": {
      "args": [
        "-y",
        "sigild"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.sigil]
command = "npx"
args = ["-y", "sigild"]

{
  "mcpServers": {
    "sigil": {
      "args": [
        "-y",
        "sigild"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "sigil": {
      "args": [
        "-y",
        "sigild"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: SIGIL_HOME (Override the default ~/.sigil directory for keyfiles, audit log, and control socket.), SIGIL_CONTROL_SOCK (Override the default control socket path (~/.sigil/control.sock).). The author declared them in the registry entry; get the values from the project itself.