F
feiyun0112/spec-coding-mcp
Spec-driven workflow that turns feature ideas
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Source
- collected from the abordage/awesome-mcp list · type: MCP server
- Harvest history
- first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
- Score
- score 1,003 · 10 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-11-05；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.
简体中文
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
# Spec Coding MCP Server
Transform feature ideas into production-ready code through systematic Spec-Driven Development
## What is Spec-Driven Development?
Spec-Driven Development is, simply put, a software development process where clear, detailed specifications serve as the core driver throughout the entire development workflow. These specifications cover various aspects such as functional requirements, performance metrics, interface definitions, and data formats of the software system, acting like blueprints in construction to clearly outline what the final software should look like for developers.
The core of spec-driven development is to transform vague requirements into an executable, traceable, and verifiable development process through standardized specification documents. Essentially, it integrates the rigor of traditional software engineering into AI programming, turning development from "vibe coding" (relying on intuition) into a controllable engineering process.
The key to spec-driven development is the "Spec folder" — each functional module corresponds to a Spec folder containing 3 core files that "materialize" requirements, designs, and tasks:
1.requirements.md (Requirements Document) — Uses EARS syntax (Easy Approach to Requirements Syntax) to write user stories and acceptance criteria, avoiding vague expressions.
2.design.md (Technical Solution) — Includes details such as architectural design, process logic, technology selection, and potential risks.
3.tasks.md (Task List) — Breaks down the technical solution into executable specific tasks (todolist).
## Implementing Spec-Driven Development with spec-coding-mcp
> The MCP in spec-coding-mcp stands for Model Context Protocol, which is an important bridge connecting external tools with the AI IDE. As long as your AI IDE can use MCP, you can use spec-coding-mcp.
Here, we'll take GitHub Copilot as an example to introduce how to use spec-coding-mcp.
### 1. Configure Vs Code
To make GitHub Copilot work with Spec-Coding-MCP, you first need to set up MCP server information in the relevant configuration files.
Visit NuGet.org, search for SpecCodingMcpServer, and you'll see the "MCP Server" tab:
Add a .vscode/mcp.json file to your Vs Code workspace, copy the json from the "MCP Server" tab into it, and save. Then click start above:
SpecCodingMcpServer requires .NET 10 to run. Please ensure you have .NET 10 installed locally (https://dotnet.microsoft.com/en-us/download/dotnet/10.0)
### 2. Start the Spec-Driven Development Process
1.Function Definition: Issue the instruction "Start spec coding" to GitHub Copilot, then specify the specific function, such as "Create a Vue to-do app", add relevant details, and proceed to the next step after confirmation.
Transform feature ideas into production-ready code through systematic Spec-Driven Development
## What is Spec-Driven Development?
Spec-Driven Development is, simply put, a software development process where clear, detailed specifications serve as the core driver throughout the entire development workflow. These specifications cover various aspects such as functional requirements, performance metrics, interface definitions, and data formats of the software system, acting like blueprints in construction to clearly outline what the final software should look like for developers.
The core of spec-driven development is to transform vague requirements into an executable, traceable, and verifiable development process through standardized specification documents. Essentially, it integrates the rigor of traditional software engineering into AI programming, turning development from "vibe coding" (relying on intuition) into a controllable engineering process.
The key to spec-driven development is the "Spec folder" — each functional module corresponds to a Spec folder containing 3 core files that "materialize" requirements, designs, and tasks:
1.requirements.md (Requirements Document) — Uses EARS syntax (Easy Approach to Requirements Syntax) to write user stories and acceptance criteria, avoiding vague expressions.
2.design.md (Technical Solution) — Includes details such as architectural design, process logic, technology selection, and potential risks.
3.tasks.md (Task List) — Breaks down the technical solution into executable specific tasks (todolist).
## Implementing Spec-Driven Development with spec-coding-mcp
> The MCP in spec-coding-mcp stands for Model Context Protocol, which is an important bridge connecting external tools with the AI IDE. As long as your AI IDE can use MCP, you can use spec-coding-mcp.
Here, we'll take GitHub Copilot as an example to introduce how to use spec-coding-mcp.
### 1. Configure Vs Code
To make GitHub Copilot work with Spec-Coding-MCP, you first need to set up MCP server information in the relevant configuration files.
Visit NuGet.org, search for SpecCodingMcpServer, and you'll see the "MCP Server" tab:
Add a .vscode/mcp.json file to your Vs Code workspace, copy the json from the "MCP Server" tab into it, and save. Then click start above:
SpecCodingMcpServer requires .NET 10 to run. Please ensure you have .NET 10 installed locally (https://dotnet.microsoft.com/en-us/download/dotnet/10.0)
### 2. Start the Spec-Driven Development Process
1.Function Definition: Issue the instruction "Start spec coding" to GitHub Copilot, then specify the specific function, such as "Create a Vue to-do app", add relevant details, and proceed to the next step after confirmation.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/feiyun0112-spec-coding-mcp/)
- Source
- awesome · https://github.com/feiyun0112/spec-coding-mcp
- Browse by field
- MCP servers
- Listed by
- 10 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.