# SpecPilot

Sets up and validates a .specs/ folder so coding agents follow architecture and project requirements.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 38
- Author: girishr
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/girishr/SpecPilot
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/mcp/specpilot

## What it does

SpecPilot brings spec-driven development into coding assistants. It scans your codebase, extracts requirements, and generates a structured `.specs/` directory. By storing architecture decisions and task trackers alongside code, it stops AI assistants from drifting away from conventions.

You can wire it up as a remote HTTP server pointing to `https://init.specpilot.dev/mcp`. There are no tokens or local installations needed for this remote mode. Alternatively, installing the npm package unlocks `specpilot serve`, which hosts a browser dashboard on port `4321` to review tasks and advance sprints.

While the remote endpoint handles onboarding immediately, local inspection utilities like `validate` or `archive` demand the global CLI binary.

## Requirements
- Remote server: `https://init.specpilot.dev/mcp`

## Install

### Claude Code (native platform)

**Platform CLI: remote server**
```bash
claude mcp add --transport http specpilot https://init.specpilot.dev/mcp
```

### Codex

**Platform CLI: remote server**
```bash
codex mcp add specpilot --url https://init.specpilot.dev/mcp
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "specpilot": {
            "url": "https://init.specpilot.dev/mcp"
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "specpilot": {
            "type": "http",
            "url": "https://init.specpilot.dev/mcp"
        }
    }
}
```

### Gemini CLI

**Platform CLI: remote server**
```bash
gemini mcp add -t http specpilot https://init.specpilot.dev/mcp
```

## When to use it
- create living architecture and task files inside `.specs/`
- onboard AI assistants into existing repositories without manual writing
- verify specification files for consistency and syntax errors
- review completed agent tasks through a local dashboard

## Example prompts
- Run project onboarding with SpecPilot and create specifications
- Check the `.specs/` folder for formatting issues and missing rules
- Initialize project specifications for a TypeScript React application

## Similar
- [REA](https://affpapa.org/en/nevibecode/mcp/rea.md) — MCP server · ★ 386989
- [GitHub](https://affpapa.org/en/nevibecode/mcp/github.md) — MCP server · ★ 33918
- [Netdata](https://affpapa.org/en/nevibecode/mcp/netdata.md) — MCP server · ★ 81115
- [browser-use](https://affpapa.org/en/nevibecode/mcp/browser-use.md) — MCP server · ★ 119160
- [Codebase Memory](https://affpapa.org/en/nevibecode/mcp/codebase-memory.md) — MCP server · ★ 47392
- [mcp-server](https://affpapa.org/en/nevibecode/mcp/mcp-server.md) — MCP server · ★ 43872

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md