Sdd MCP

Name: Sdd MCP
Author: juanklagos

作者：juanklagos版本 2.8.0i★ –i在你的电脑上运行

注册名称io.github.juanklagos/sdd-mcp

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： SDD_PROJECT_ROOT, SDD_WORKSPACES_ROOT

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

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

在终端中运行这条命令

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

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

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.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 juanklagos 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32742 个服务器的 0%
发布到注册中心的时间比此分类中其他 32742 个服务器的 30% 更新
基础检查结果等于或优于此分类中其他 32742 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Sdd MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（2.8.0）于2个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Asset Notation

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

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

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

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

在云端运行★ 211前天更新

安装

Asset Notation

作者：assetnotation

Read and maintain an Asset Notation file on disk: net worth, holdings, valuations, CSV import.

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

🌱 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

只显示了开头部分；其余内容请在仓库中阅读