# sdd-mcp [Health: Active]

**Category:** 📋 Product Management  
**Repository:** https://github.com/juanklagos/spec-driven-development-template  
**GitHub Stars:** 21  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/sdd-mcp

## Description
Spec-Driven Development workflow: specs, plans, gates, status and logbook tools. Bilingual EN/ES.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "sdd-mcp": {
    "command": "npx",
    "args": ["-y","@juanklagos/create-sdd-project@latest"]
  }
}
```

## Documentation

## What sdd-mcp does

The sdd-mcp MCP server brings the repository’s Spec-Driven Development workflow into an AI agent through MCP tools. Its focus is the work that happens before and around implementation: defining a feature, preparing a plan, checking approval conditions, tracking progress, and recording decisions or session history.

The workflow treats written artifacts as the source of project decisions. A feature is organized into a numbered bundle containing a specification, plan, tasks, and history. The repository also uses a `bitacora/` logbook to preserve session context and decisions for later review.

The central policy is that implementation should not begin until an approved `spec.md` and a consistent `plan.md` are present, with user consent recorded. This makes the server relevant for teams using AI coding agents that need a clear boundary between requirements and code changes.

## How it works

The workflow starts with an idea expressed in plain language. The agent then helps create or refine a specification, including acceptance criteria, and prepares a plan that matches the approved scope. Tasks can be prioritized before the workflow reaches its gate.

At the gate, the project checks approval, plan consistency, and recorded consent. The repository provides shell scripts for policy checks, gate validation, and consent recording; the MCP connector allows an AI tool to operate the workflow rather than relying only on manual commands.

After implementation, validation and logbook updates complete the cycle. Decisions can be written to `bitacora/decisiones/`, including the decision, rationale, rejected alternatives, and a possible revisit point.

## Tools and capabilities

- Creating and managing specifications.
- Preparing and reviewing implementation plans.
- Running or working with approval gates.
- Checking workflow status and identifying the next step.
- Recording decisions and session history in the logbook.
- Supporting the broader SDD process in English and Spanish.

The repository also includes related agent workflows outside MCP. Claude Code commands cover help, new specifications, spec refinement, gate execution, decisions, session closure, and tutoring. VS Code and Copilot use prompt files, while a portable Agent Skill supports any agent that can consume it. These companion entry points are part of the repository’s wider workflow and should not be confused with the MCP tool surface.

## Setup and configuration

The repository describes three ways to apply the workflow to a project: a compact `spec/` sidecar for an existing codebase, an internal workspace, or a full standalone copy. A project can also be scaffolded with `npx @juanklagos/create-sdd-project@latest`, which asks configuration questions and creates the selected project structure.

For an existing project, the sidecar approach keeps application code in its current location while placing SDD artifacts under `./spec/`. The repository also documents shell scripts for installing a sidecar, creating a workspace, initializing a project, checking policy alignment, validating the SDD gate, and recording consent.

## Limitations and notes

The sdd-mcp MCP server is tied to the repository’s documented SDD conventions, including numbered spec bundles, approval records, plan consistency, and the `bitacora/` logbook. It is best suited to projects willing to keep these artifacts under version control.

Exact tool names and client configuration therefore cannot be inferred from this listing alone.

The repository is MIT licensed and includes bilingual English and Spanish learning material. Its broader template also builds on GitHub Spec Kit for step-by-step commands and workflow structure.

_Full upstream README: https://allmcps.com/mcp/sdd-mcp/readme_