MCP.so
登录
S

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

常见问题

1

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.

2

What are the runtime requirements?

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

3

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.

4

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`.

5

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.

评论

其他 分类下的更多 MCP 服务器