spec-driven-mcp

# Spec-Driven MCP Server Your living source-of-truth for product & engineering specs — built for **VS Code + AI agents**. **Markdown specs → SQLite → dashboard → MCP tools.** --- ## Why use this? * Centralize **requirements**, **acceptance criteria**, and **non-functional** specs in one place. * Track verification with **pass/fail events**; roll-ups show what's **VERIFIED / FAILING / PARTIAL / UNTESTED**. * Give AI agents safe MCP access to **read, search, edit, and record verification**. * **Auto-launching dashboard** provides instant web UI access from VS Code. * Lightweight **HTML dashboard** (Tailwind + htmx/Alpine) for quick browsing and edits. --- ## Quick start ### 1) Install the tool We recommend **pipx** so the CLI is on your PATH without virtualenv chores: ```bash pipx install spec-driven-mcp ``` Or with pip: ```bash pip install spec-driven-mcp ``` ### 2) Add this to `.vscode/mcp.json`: ```jsonc { "servers": { "specs-mcp": { "type": "stdio", "command": "spec-mcp-stdio" } } } ``` **Custom Database Location:** To use a specific database file: ```jsonc { "servers": { "specs-mcp": { "type": "stdio", "command": "spec-mcp-stdio", "args": ["--db-path", "/path/to/your/specs.db"] } } } ``` Open Copilot Chat → Agent mode, start the server from **MCP Servers** and use the tools/resources. **🚀 Dashboard Auto-Start:** The MCP server automatically starts the web dashboard in the background at **http://localhost:8765** when launched from VS Code. No separate dashboard command needed! --- ## Defaults that "just work" * **Database location:** Uses intelligent directory detection with robust fallbacks: 1. **Project-local**: `<current-directory>/.spec-mcp/specs.db` when running from a project directory 2. **User data directory**: Platform-specific fallback ensures consistency across invocations 3. **Custom path**: Override wit…