Sdd MCP

Name: Sdd MCP
Author: juanklagos

by juanklagosversion 2.8.0i★ –iRuns on your computer

Registry nameio.github.juanklagos/sdd-mcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: SDD_PROJECT_ROOT, SDD_WORKSPACES_ROOT

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "sdd": {
      "command": "npx",
      "args": [
        "-y",
        "@juanklagos/sdd-mcp"
      ],
      "env": {
        "SDD_PROJECT_ROOT": "your-value",
        "SDD_WORKSPACES_ROOT": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add sdd --env SDD_PROJECT_ROOT=your-value --env SDD_WORKSPACES_ROOT=your-value -- npx -y @juanklagos/sdd-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "sdd": {
      "command": "npx",
      "args": [
        "-y",
        "@juanklagos/sdd-mcp"
      ],
      "env": {
        "SDD_PROJECT_ROOT": "your-value",
        "SDD_WORKSPACES_ROOT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "sdd": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@juanklagos/sdd-mcp"
      ],
      "env": {
        "SDD_PROJECT_ROOT": "your-value",
        "SDD_WORKSPACES_ROOT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

SDD_PROJECT_ROOT env
Path to the SDD workspace (project with specs/ or a spec/ sidecar). Defaults to the current working directory.
SDD_WORKSPACES_ROOT env
Where sdd_create_workspace creates ./www/ . Defaults to the current working directory.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account juanklagos, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32727 servers in this category
Published to the registry more recently than 30% of the other 32727 servers in this category
Basic checks equal to or better than 100% of the other 32727 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Sdd MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.8.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Foliosio

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Foliosio

by foliosio.com

Read your support inbox, tag conversations and save draft replies from your AI agent. Never sends.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

🌱 Spec-Driven Development Template

Learn Spec-Driven Development, then use it on real projects. One rule: no code until you approve a written spec. A script checks that rule every time you run it, and prints exactly what it looked at.

🇺🇸 English · 🇪🇸 Español

Non-technical start · Quickstart · AI agent start · Commands · Community

What is this?

Spec-Driven Development (SDD) means writing and approving a clear specification *before* any code exists. What you decided ends up in a file, instead of buried in a chat you will close and never find again. By 2026 it is how most people build software with AI agents.

This repo does double duty.

It is a school: a bilingual (EN/ES) path that starts from zero, with guides, an interactive course and a tutor you can talk to. You do not need to know how to program to get through it.

It is also a toolkit for real work: scripts that check the rule, instruction files your AI assistant reads, a connector so your AI tool can run the workflow itself (MCP, the Model Context Protocol), and a single spec/ folder you add to a project that already has code — without moving any of it.

The step-by-step commands come from GitHub Spec Kit. This repo adds the guides, the checks and the templates on top of them.

The flow in action — create a spec, validate, pass the gate *(regenerated on every release)*:

What changes in practice: decisions stop living in chat history and move into specs/. The gate stays closed until spec.md and plan.md exist, agree, and you record your consent — a script checks that, not somebody's memory. A new teammate or a new agent lands in a folder layout they already recognize. And bitacora/ keeps the session log, so six months later you can still find out why something was done the way it was.

Want the industry map? Read SDD in 2026: state of the art and how this template compares.

Choose your door

Non-technical (founder, PM, curious): START_HERE_NON_TECH.md — a guided start with no jargon in it.
Developer: QUICKSTART.md — the commands to scaffold and validate, about five minutes.
AI agent, or you pasting into one: AI_START_HERE.md — operating rules plus copy/paste prompts for each level.

Then pick your learning level. Every guide on the docs site carries its level badge:

🟢 Beginner: quick guide for non-programmers
🟡 Intermediate: team discipline guide
🔴 Advanced: governance and standardization

[!TIP]

If you would rather learn by doing, take the [interactive course](https://github.com/juanklagos/aprende-sdd) (GitHub Skills format): 4 steps, ~35 min, auto-graded by Actions. Your exam is the real SDD gate.

Start in 30 seconds

Copy/paste this prompt into your AI assistant (Claude, Cursor, Copilot, Gemini...):

Using https://github.com/juanklagos/spec-driven-development-template, guide me step by step with SDD for my project.

My project is: [describe your project in plain language]. If my project is new, initialize from this template and GitHub Spec Kit as the base workflow. If it already exists, adapt it without breaking current behavior. No code before approved spec and consistent plan.

Built-in commands for your AI agent

If you use Claude Code, this repo ships slash commands out of the box. Start with /sdd:help:

Command	What it does
`/sdd:help`	Tells you what stage you are in and the single next step
`/sdd:new`	Guided start: idea → first spec ready for approval
`/sdd:spec`	Create or refine a spec bundle with EARS criteria
`/sdd:gate`	Runs the gate — approval, plan consistency, consent — and records yours
`/sdd:decision`	One decision, written down in `bitacora/decisiones/`: what, why, what was rejected, when to revisit
`/sdd:close`	Validates and closes the session with the output contract
`/sdd:tutor`	A conversational SDD course by levels, graded by the real validation scripts

Install in any project as a plugin (no cloning):

/plugin marketplace add juanklagos/spec-driven-development-template

/plugin install sdd@sdd-template

VS Code / Copilot: the same flows as prompt files in .github/prompts/.
Any agent (39 tools): portable Agent Skill at skills/sdd-workflow/SKILL.md.
AI context: llms.txt indexes all docs for coding agents (regenerate with ./scripts/generate-llms-txt.sh).

The golden rule

[!IMPORTANT]

No code before an approved `spec.md` and a consistent `plan.md`.

A script enforces this, and implementation starts only once your consent is on record.

./scripts/check-sdd-policy.sh .   # multi-agent policy files are aligned

./scripts/check-sdd-gate.sh . # spec approved + plan consistent + consent recorded ./scripts/confirm-user-consent.sh --spec 001- "User approved scope X"

(In sidecar projects the same scripts live under ./spec/scripts/.)

Enforce it in CI too. This repo doubles as a GitHub Action, listed on the GitHub Marketplace:

- uses: juanklagos/spec-driven-development-template@v2.8.0

with: path: "." # project root (sidecar or standalone auto-detected) strict: "true"

Reference files: sdd.policy.yaml · INSTRUCTIONS.md · AGENT_OPERATING_SYSTEM.md

How it works

flowchart LR

A["💡 Idea in plain language"] --> B["📋 spec.md approved"] B --> C["🗺️ plan.md consistent"] C --> D["✅ tasks.md prioritized"] D --> E["🚦 Gate + explicit consent"] E --> F["⚙️ Implementation"] F --> G["🔍 Validation + logbook"]

Every feature gets a numbered spec bundle, and every session leaves a trace in bitacora/ (the logbook):

spec.md — what and why *(approved by you)*
plan.md — how *(consistent with the spec)*
tasks.md — concrete steps
history.md — how it evolved

Full walkthrough example: examples/002-mcp-end-to-end

Apply it to a real project

Fastest start (no clone needed):

npx @juanklagos/create-sdd-project@latest my-app

It asks a few questions and scaffolds the recommended spec/ sidecar, or a full workspace, from the latest template.

Three ways to use the template, from lightest to heaviest:

Mode	When	Command
Compact `spec/` sidecar ⭐	Real or existing project: SDD artifacts in `./spec/`, code stays in your project root	`./scripts/install-spec-sidecar.sh /path/to/project --profile=recommended`
Internal workspace `www/`	The runnable project should live inside this template repo	`./scripts/create-www-project.sh my-project codex`
Full standalone copy	You explicitly want the whole framework as your workspace	`./scripts/init-project.sh /path/to/project --profile=full`

[!TIP]

The professional default is the compact spec/ sidecar and nothing else. Never copy the full framework into a real codebase unless you actually want standalone mode.

Everyday commands (sidecar mode shown; the same scripts exist at root in standalone mode)

Action	Command
New spec	`./spec/scripts/new-spec.sh "my-feature" "Owner"`
Validate structure	`./spec/scripts/validate-sdd.sh . --strict`
Policy check	`./spec/scripts/check-sdd-policy.sh .`
SDD gate	`./spec/scripts/check-sdd-gate.sh .`
Status dashboard	`./spec/scripts/generate-status.sh`

Folder anatomy and layout details: project organization map

flowchart TD

A["Your project root (code)"] --> B["spec/"] B --> C["idea/"] B --> D["specs/ (numbered bundles)"] B --> E["bitacora/ (logbook)"] B --> F["scripts/ (gate + validation)"]

Connect via MCP (optional, advanced)

If your AI tool supports MCP (the Model Context Protocol), it can run this workflow itself: create specs, check the gate, write the logbook. One command sets it up, in your project's folder:

npx @juanklagos/sdd-mcp@latest connect

It finds the clients you have — Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, opencode — and writes the configuration into each one's own file. It merges into what you already have and never overwrites it. Add --dry-run first to see what it would touch. Then restart your client.

Prefer doing it by hand? Point your client at npm: {"command": "npx", "args": ["-y", "@juanklagos/sdd-mcp@latest"]}. The @latest matters — without it, npx can serve an old cached version with fewer tools.
Working on this template itself? npm install && npm run build && npm run mcp:start runs the server from source.
SDD Builder (visual, drag-and-drop): build once with npm run builder:build, then SDD_PROJECT_ROOT=/path/to/your/project npm run mcp:http:start and open http://127.0.0.1:3334/builder — compose your specs as connected cards, where every card is a real specs/NNN/ bundle on disk. Inside this template repository the builder is blocked by design (no target-project work in the template root), so always point SDD_PROJECT_ROOT at a real workspace. See the visual guide.
Already using SDD and want the latest? npx @juanklagos/sdd-mcp@latest upgrade --project-root . --dry-run shows what would change before changing it: framework files get repaired, yours are never written without --apply. See the upgrade guide.
SDD Desk (the same builder, as a desktop app): download it for macOS, Windows or Linux. Nothing else has to be installed: the app includes everything it needs. While it is open, your

Only the beginning is shown; read the rest in the repo

Sdd MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Foliosio

README from the maker

🌱 Spec-Driven Development Template

What is this?

Choose your door

Start in 30 seconds

Built-in commands for your AI agent

The golden rule

How it works

Apply it to a real project