Developer Tools

specpilot.dev

Generates project specifications by returning unanswered onboarding questions and producing complete SpecPilot specs based on supplied answers.

1 endpoint2 known toolsFirst detected September 13, 2026Last detected September 13, 2026

ENDPOINT 1

https://init.specpilot.dev/mcp

No auth detected

MCP server metadata

Name: specpilot
Version: 1.0.0

Capabilities

tools.listChangedprompts.listChanged

Known tools 2

specpilot_next_questions

Returns the still-unanswered SpecPilot onboarding questions of the next incomplete step, gated by the answers supplied so far - questions that do not apply to this kind of project are omitted, and options are filtered, badged or flagged the same way the SpecPilot web chat would.

Inferred read-only

specpilot_generate_specs

Generates the complete SpecPilot .

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.specpilot]
url = "https://init.specpilot.dev/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "specpilot": {
      "type": "http",
      "url": "https://init.specpilot.dev/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: specpilot
Remote MCP URL: https://init.specpilot.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "specpilot": {
      "url": "https://init.specpilot.dev/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "specpilot": {
      "type": "http",
      "url": "https://init.specpilot.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "specpilot",
  "transport": "streamable-http",
  "url": "https://init.specpilot.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.