Sdd MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 108 installs a week from npm. Last commit 31 Aug 2026.
Spec-Driven Development workflow: specs, plans, gates, status and logbook tools. Bilingual EN/ES.
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
return path.join(sddRoot, rel);
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add sdd-mcp -- npx -y @juanklagos/sdd-mcp
{
"mcpServers": {
"sdd-mcp": {
"command": "npx",
"args": [
"-y",
"@juanklagos/sdd-mcp"
]
}
}
}
[mcp_servers.sdd-mcp]
command = "npx"
args = ["-y", "@juanklagos/sdd-mcp"]
{
"mcpServers": {
"sdd-mcp": {
"command": "npx",
"args": [
"-y",
"@juanklagos/sdd-mcp"
]
}
}
}
{
"servers": {
"sdd-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@juanklagos/sdd-mcp"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
SDD_PROJECT_ROOT (Path to the SDD workspace (project with specs/ or a spec/ sidecar). Defaults to the current working directory), SDD_WORKSPACES_ROOT (Where sdd_create_workspace creates ./www/<project-name>. Defaults to the current working directory).
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
Spec-driven development locally: specs, constitutions, plans, tasks, git and quality checks.
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Spec-driven dev workflow MCP: start_* orchestration, memory, GitNexus, quality gates.
Spec-driven development MCP server: 8 phases, bi-directional traceability, 7 quality gates.
Spec-driven development for AI coding agents: live requirements, stories and traceability over MCP
Work management with Spec-Driven Development: tasks, sprints and SDD approvals for coding agents.
Spec-driven development for AI coding agents: specs, skills, agents, rules and MCP servers.
Answers built from our own checks of this server.