Spec-Driven Development MCP Server

@formulahendry

リポジトリ

基本情報

カテゴリ

その他

トランスポート

stdio

作者

formulahendry

投稿者

Jun Han

Spec-Driven Development MCP Server について

Spec-Driven Development MCP Server, no just Vibe Coding

Spec-Driven Development MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

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

Spec-Driven Development MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。

概要

What is Spec-Driven Development MCP Server?

A Model Context Protocol (MCP) server that provides structured prompts for generating requirements, design documents, and code in a systematic spec-driven development workflow. It is intended for developers who want to move from ad‑hoc “vibe coding” to a traceable, specification‑first approach.

How to use Spec-Driven Development MCP Server?

Requires Node.js 20+. Install by adding the server configuration in mcp.json (command: npx, args: ["-y","mcp-server-spec-driven-development@latest"]) or by clicking the VS Code install buttons in the README. Invoke the three available prompts in order: generate-requirements, generate-design-from-requirements, generate-code-from-design.

Key features of Spec-Driven Development MCP Server

Structured workflow: requirements → design → code
Uses EARS (Easy Approach to Requirements Syntax) format
Integrates with any MCP‑compatible tool (VS Code, etc.)
Generates markdown files in a specs/ folder

Use cases of Spec-Driven Development MCP Server

Creating a formal requirements document from high‑level user stories
Deriving a design document directly from previously written requirements
Generating implementation code that is traceable back to a design
Enforcing a consistent spec‑driven process in team projects

よくある質問

What problem does this server solve?

It replaces unstructured “vibe coding” with a reproducible, spec‑driven workflow where requirements, design, and code are linked, improving clarity and maintainability.

What are the runtime requirements?

Node.js version 20 or later. No other external services or databases are mentioned.

Where are the generated files saved?

`generate-requirements` writes to `specs/requirements.md`; `generate-design-from-requirements` writes to `specs/design.md`; `generate-code-from-design` writes implementation files into the project root folder.

Does this server require any paid subscriptions or API keys?

No. The README lists no API keys, authentication, or paid tiers. It runs entirely via `npx`.

How is this different from a regular code‑generation tool?

It enforces a three‑step process (requirements → design → code) using the EARS format, ensuring every line of code is traceable back to a written requirement.

「その他」の他のコンテンツ

Reactive Resume

amruthpillai

A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!

39.5K

🚀 Model Context Protocol (MCP) Curriculum for Beginners

microsoft

This open-source curriculum introduces the fundamentals of Model Context Protocol (MCP) through real-world, cross-language examples in .NET, Java, TypeScript, JavaScript, Rust and Python. Designed for developers, it focuses on practical techniques for building modular, scalable,

16.7K