# io.github.juanklagos/sdd-mcp (npm · @juanklagos/sdd-mcp)

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

- Trust score: 64/100 (medium)
- Change this week: +45
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-07

## Components

- npm · `@juanklagos/sdd-mcp`: 64/100 (this document), [markdown](https://verifymcp.io/servers/juanklagos-sdd-mcp/juanklagos-sdd-mcp.md), [page](https://verifymcp.io/servers/juanklagos-sdd-mcp/juanklagos-sdd-mcp)

## Channel facts

- Registry: `npm`
- Package: `@juanklagos/sdd-mcp`
- Version: `2.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-07.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Known CVEs were checked across the 98 of 102 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Dependency health was assessed across the 98 of 102 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 15 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 47/100
  - 7% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1767 tokens (~65/item across 27 items; 21 tools + 6 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 74% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### Claude

```bash
claude mcp add juanklagos-sdd-mcp -- npx -y @juanklagos/sdd-mcp
```

### Codex

```bash
codex mcp add juanklagos-sdd-mcp -- npx -y @juanklagos/sdd-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "juanklagos-sdd-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@juanklagos/sdd-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add juanklagos-sdd-mcp --command npx --arg -y --arg @juanklagos/sdd-mcp
```

### Hermes

```yaml
mcp_servers:
  juanklagos-sdd-mcp:
    command: "npx"
    args: ["-y", "@juanklagos/sdd-mcp"]
```

### Other

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-06 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-05 (score 63, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-08-04 (score 63, +4)

- [functional regression] Security disclosure: fail → unverified
- [functional improvement] Stability: unverified → 0.27

### 2026-08-02 (score 59, +54)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Schema quality: unverified → 7
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → good
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] License: unverified → pass
- [functional] First check of Capabilities: pass
- [functional] Licence: MIT

### 2026-08-01 (score 5, −14)

- [functional regression] Schema quality: 7 → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-07-31 (score 19, −24)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-27 (score 43)

First indexed and scored.

## MCP tools (21)

### `sdd_create_workspace` (~58 tokens)

Create SDD workspace

Create a runnable SDD workspace inside the recommended default folder ./www/<project-name>.

Input parameters:

- `assistant` (string)
- `profile` (string)
- `projectName` (string, required)
- `useSpecKit` (boolean)

Output parameters:

- `assistant` (string)
- `layout` (string)
- `profile` (string)
- `projectRoot` (string)
- `sddRoot` (string)
- `usedSpecKit` (boolean)

### `sdd_create_spec` (~59 tokens)

Create numbered spec

Create the next numbered spec folder from the template.

Input parameters:

- `featureName` (string, required)
- `owner` (string)
- `projectRoot` (string, required): Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Output parameters:

- `indexUpdated` (boolean)
- `specDir` (string)
- `specId` (string)

### `sdd_validate` (~45 tokens)

Validate SDD project

Validate the SDD structure and required files of a project.

Input parameters:

- `projectRoot` (string, required): Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Output parameters:

- `errors` (number)
- `messages` (array)
- `ok` (boolean)
- `warnings` (number)

### `sdd_check_gate` (~44 tokens)

Check SDD gate

Verify whether implementation can proceed under SDD rules.

Input parameters:

- `projectRoot` (string, required): Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Output parameters:

- `approvedSpecs` (number)
- `errors` (number)
- `messages` (array)
- `ok` (boolean)
- `totalSpecs` (number)
- `verdict` (string)
- `warnings` (number)

### `sdd_record_user_consent` (~101 tokens)

Record user consent

Record explicit user consent before implementation starts. Pass specId so the consent is bound to that spec; without it the entry is a legacy, markerless line that only covers specs approved before it.

Input parameters:

- `projectRoot` (string, required): Absolute target project path. Recommended default inside this template: ./www/<project-name>.
- `specId` (string): Numbered spec folder id such as 001-my-feature.
- `summary` (string, required)

Output parameters:

- `logFile` (string)
- `summary` (string)
- `timestamp` (string)

### `sdd_list_specs` (~42 tokens)

List SDD specs

List numbered specs and their approval status.

Input parameters:

- `projectRoot` (string, required): Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Output parameters:

- `specs` (array)

### `sdd_generate_status` (~46 tokens)

Generate status dashboard

Generate STATUS.md from the current project specs and logbook.

Input parameters:

- `projectRoot` (string, required): Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Output parameters:

- `content` (string)
- `path` (string)

### `sdd_generate_roadmap` (~55 tokens)

Generate roadmap

Generate docs/roadmap.mmd and docs/roadmap.md from specs/INDEX.md.

Input parameters:

- `projectRoot` (string, required): Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Output parameters:

- `markdown` (string)
- `markdownPath` (string)
- `mermaid` (string)
- `mermaidPath` (string)

### `sdd_append_project_log` (~54 tokens)

Append project log entry

Append content to bitacora/global/PROJECT_LOG.md.

Input parameters:

- `entry` (string, required)
- `projectRoot` (string, required): Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Output parameters:

- `content` (string)
- `path` (string)

### `sdd_write_daily_log` (~68 tokens)

Write daily log

Create or replace a daily log entry in bitacora/diaria.

Input parameters:

- `content` (string, required)
- `date` (string, required): Use YYYY-MM-DD.
- `projectRoot` (string, required): Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Output parameters:

- `content` (string)
- `path` (string)

### `sdd_write_handoff` (~81 tokens)

Write handoff

Create or replace a handoff file in bitacora/handoffs.

Input parameters:

- `content` (string, required)
- `fileName` (string, required): Use a markdown filename such as 2026-03-18-handoff.md.
- `projectRoot` (string, required): Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Output parameters:

- `content` (string)
- `path` (string)

### `sdd_write_decision` (~80 tokens)

Write decision

Create or replace a decision file in bitacora/decisiones.

Input parameters:

- `content` (string, required)
- `fileName` (string, required): Use a markdown filename such as 2026-03-18-decision.md.
- `projectRoot` (string, required): Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Output parameters:

- `content` (string)
- `path` (string)

### `sdd_board_read` (~63 tokens)

Read SDD board

Read the visual SDD Builder board: the specs/board.canvas layout (JSON Canvas) plus every spec with its approval status and task progress.

Input parameters:

- `projectRoot` (string, required): Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Output parameters:

- `canvas` (object)
- `specs` (array)

### `sdd_board_write` (~70 tokens)

Write SDD board

Replace the specs/board.canvas layout (JSON Canvas: nodes + edges). Only layout is stored; markdown files are never touched by this tool.

Input parameters:

- `canvas` (object, required)
- `projectRoot` (string, required): Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Output parameters:

- `edges` (number)
- `nodes` (number)
- `ok` (boolean)

### `sdd_board_connect` (~99 tokens)

Connect board cards

Connect two existing board cards with an optional labeled edge and persist specs/board.canvas. Idempotent for identical edges.

Input parameters:

- `fromNode` (string, required): Source node id, e.g. a spec id like 001-my-feature.
- `label` (string)
- `projectRoot` (string, required): Absolute target project path. Recommended default inside this template: ./www/<project-name>.
- `toNode` (string, required): Target node id.

Output parameters:

- `canvas` (object)

### `sdd_read_tasks` (~71 tokens)

Read spec tasks

Read the checkbox tasks of a spec's tasks.md with their line numbers and done state.

Input parameters:

- `projectRoot` (string, required): Absolute target project path. Recommended default inside this template: ./www/<project-name>.
- `specId` (string, required): Numbered spec folder id such as 001-my-feature.

Output parameters:

- `specId` (string)
- `tasks` (array)

### `sdd_set_task_done` (~107 tokens)

Set spec task done

Toggle one checkbox line in a spec's tasks.md (surgical edit, atomic write) and return the updated tasks.

Input parameters:

- `done` (boolean, required)
- `line` (integer, required): Zero-based line number of the task, as returned by sdd_read_tasks.
- `projectRoot` (string, required): Absolute target project path. Recommended default inside this template: ./www/<project-name>.
- `specId` (string, required): Numbered spec folder id such as 001-my-feature.

Output parameters:

- `specId` (string)
- `tasks` (array)

### `sdd_gate_summary` (~94 tokens)

Gate semaphore summary

One-call gate semaphore: runs the SDD gate check plus the structural validation and groups every message by the spec it belongs to (the same data the SDD Builder chip and per-card badges show). Includes advisory dependencyWarnings from the board's typed edges (approved spec depending on a not-approved one).

Input parameters:

- `projectRoot` (string, required): Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Output parameters:

- `approvedSpecs` (number)
- `dependencyWarnings` (array)
- `errors` (number)
- `gate` (object)
- `generalIssues` (array)
- `ok` (boolean)
- `specIssues` (object)
- `totalSpecs` (number)
- `validation` (object)
- `verdict` (string)
- `warnings` (number)

### `sdd_approve_spec` (~142 tokens)

Approve spec

Surgically fill the existing approval block of a spec.md: Estado -> Aprobado, approval date -> today, approver -> given name, evidence when provided (always wins) or when the line is empty. Fails clearly when the block is missing.

Input parameters:

- `approver` (string, required): Person or role approving the spec.
- `evidence` (string): Approval evidence (link or short quote); overwrites the evidence line when given.
- `projectRoot` (string, required): Absolute target project path. Recommended default inside this template: ./www/<project-name>.
- `specId` (string, required): Numbered spec folder id such as 001-my-feature.

Output parameters:

- `approvalDate` (string)
- `approver` (string)
- `evidenceUpdated` (boolean)
- `fieldsUpdated` (array)
- `specId` (string)
- `status` (string)

### `sdd_update_spec_sections` (~222 tokens)

Update spec sections

Replace ONLY the content under the guided-editor headings of a spec.md (user story, acceptance scenarios, EARS criteria, requirements, spec properties, success criteria, out of scope — the full template) preserving everything else, the approval block included. Tolerant to the EN/ES headings of the canonical repo template (specs/_template/spec.md).

Input parameters:

- `criteria` (array): EARS acceptance criteria (bullet list).
- `outOfScope` (string): Out of scope (free text).
- `projectRoot` (string, required): Absolute target project path. Recommended default inside this template: ./www/<project-name>.
- `properties` (array): Spec properties — universal, testable properties (bullet list).
- `requirements` (array): Requirements (bullet list).
- `scenarios` (array): Acceptance scenarios (numbered list).
- `specId` (string, required): Numbered spec folder id such as 001-my-feature.
- `story` (string): Main user story (free text).
- `successCriteria` (array): Success criteria (bullet list).

Output parameters:

- `created` (array)
- `specId` (string)
- `updated` (array)

### `sdd_board_app` (~84 tokens)

Show SDD board

Show the visual SDD board inside the client (MCP Apps): spec cards with approval status and task progress, board connections, the gate semaphore and dependency warnings. Read-only view; hosts without MCP Apps support get the same data as JSON text.

Input parameters:

- `projectRoot` (string, required): Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Output parameters:

- `board` (object)
- `gate` (object)
- `projectRoot` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/juanklagos-sdd-mcp/juanklagos-sdd-mcp#diagnostics

## Score history

- 2026-08-07: 64
- 2026-08-06: 64
- 2026-08-05: 63
- 2026-08-04: 63
- 2026-08-03: 59
- 2026-08-02: 59
- 2026-08-01: 5
- 2026-07-31: 19
- 2026-07-30: 43
- 2026-07-28: 43
- 2026-07-27: 43

## Links

- npm package: https://www.npmjs.com/package/@juanklagos/sdd-mcp
- Socket report: https://socket.dev/npm/package/@juanklagos/sdd-mcp
- Repository: https://github.com/juanklagos/spec-driven-development-template
- Changelog RSS feed: https://verifymcp.io/servers/juanklagos-sdd-mcp/juanklagos-sdd-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/juanklagos-sdd-mcp/juanklagos-sdd-mcp.json
- HTML version of this page: https://verifymcp.io/servers/juanklagos-sdd-mcp/juanklagos-sdd-mcp