Spec Driven Development

Name: Spec Driven Development
Author: formulahendry

by formulahendryversion 0.1.1i★ 440iRuns on your computer

Registry nameio.github.formulahendry/spec-driven-development

Overview

Description from the maker (original English)

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

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 checksi2 of 3 passedChecked from public information; code not scanned yet
UsageiEarly★ 440

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.

You need

npmNode.js installed (for the npx command)

Claude DesktopClaude CodeCursorVS Code

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

{
  "mcpServers": {
    "spec-driven-development": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-spec-driven-development"
      ]
    }
  }
}

Run this in your terminal

claude mcp add spec-driven-development -- npx -y mcp-server-spec-driven-development

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

{
  "mcpServers": {
    "spec-driven-development": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-spec-driven-development"
      ]
    }
  }
}

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "spec-driven-development": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-spec-driven-development"
      ]
    }
  }
}

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

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 5, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account formulahendry, which owns the repo
✕ Fail
Still maintained
No code changes for over a year, or the repo is archived
✓ Pass
Has a licence
Uses MIT
– 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
Needs the server’s tool list first; this check starts in the next step

Compared with others in Otheri

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

Compared only with servers in this prototype, not the whole registry.

Common questions

Is Spec Driven Development safe?

It passed 2 of 3 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 13 months ago, and the latest version (0.1.1) reached the registry 13 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: Remote Desktop Commander

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

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 today

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 MCP Server

-VS_Code-0098FF)

Model Context Protocol (MCP) server that facilitates spec-driven development workflows by providing structured prompts for generating requirements, design documents, and code following a systematic approach.

🎯 Purpose

This MCP server enables developers to follow a structured spec-driven development approach by providing prompts that guide you through:

Requirements Generation - Create detailed requirements documents using the EARS (Easy Approach to Requirements Syntax) format
Design Generation - Generate design documents based on requirements
Code Generation - Generate implementation code based on design documents

✨ Features

Structured Workflow: Follows a clear progression from requirements → design → code
EARS Format Support: Uses industry-standard EARS format for requirements documentation
MCP Protocol: Integrates seamlessly with MCP-compatible tools and environments

🚀 Quick Start

Prerequisites

Node.js 20+

Installation

VS Code

Install the MCP server in VS Code using below buttons:

-VS_Code-0098FF) -VS_Code_Insiders-24bfa5)

Alternatively, you can add configuration in mcp.json:

"servers": { "spec-driven": { "command": "npx", "args": [ "-y", "mcp-server-spec-driven-development@latest" ] } } }

Cursor, Claude Code

Install the MCP server in Cursor using below button:

Alternatively, you can add configuration in mcp.json:

"mcpServers": { "spec-driven": { "command": "npx", "args": [ "-y", "mcp-server-spec-driven-development@latest" ] } } }

📋 Available Prompts

1. Generate Requirements Document

Name: generate-requirements
Description: Generate requirements.md using EARS format
Input: High-level requirements of the application. Example: 'A Vue.js todo application with task creation, completion tracking, and local storage persistence'
Output: Structured requirements document in specs/requirements.md

2. Generate Design from Requirements

Name: generate-design-from-requirements
Description: Generate design.md from requirements.md
Input: Reads from specs/requirements.md
Output: Design document in specs/design.md

3. Generate Code from Design

Name: generate-code-from-design
Description: Generate code from design.md
Input: Reads from specs/design.md
Output: Implementation code in the root folder

📖 Workflow Example

Start with Requirements: Use the generate-requirements prompt with your initial requirements text
Create Design: Use generate-design-from-requirements to create a design document based on your requirements
Generate Code: Use generate-code-from-design to generate implementation code from your design

This creates a traceable path from requirements through design to implementation, ensuring consistency and completeness in your development process.

🤔 Why Spec-Driven Development?

Moving beyond Vibe Coding to a structured, specification-driven approach brings clarity, consistency, and maintainability to your development workflow. Instead of coding by intuition alone, Spec-Driven Development provides a systematic foundation that scales with your project's complexity.

Learn more about the benefits: Goodbye, Vibe Coding! Hello, Spec-Driven Development MCP Server!