Specter Skills MCP Server

What the code does

We read the source, 20 h ago · rules 3dff92dd89df

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    spawn(cmd, args, { stdio: 'ignore', detached: true }).unref();

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 specter-skills -- npx -y specter-skills

{
  "mcpServers": {
    "specter-skills": {
      "args": [
        "-y",
        "specter-skills"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.specter-skills]
command = "npx"
args = ["-y", "specter-skills"]

{
  "mcpServers": {
    "specter-skills": {
      "args": [
        "-y",
        "specter-skills"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "specter-skills": {
      "args": [
        "-y",
        "specter-skills"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: SPECTER_ENV (Target environment: 'staging' or 'production'), SPECTER_ALLOW_MUTATIONS (Set 'true' to enable the create/mutate tools (gated behind confirmation)), SPECTER_API_KEY (Client api-key. Not needed after browser sign-in (the dev key from login is reused)), SPECTER_PROJECT_ID (Auto-detected from sign-in. Set only to pin one project when your org has several), SPECTER_ADMIN_TOKEN (Admin token for CI / non-interactive use instead of browser sign-in). The author declared them in the registry entry; get the values from the project itself.