Skip to content
Back to search

specs-workflow-mcp

Intelligent spec workflow management MCP server

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/kingkongshot--specs-workflow-mcp/badge.svg)](/listings/kingkongshot--specs-workflow-mcp)

HTML

<a href="/listings/kingkongshot--specs-workflow-mcp"><img src="/api/listings/kingkongshot--specs-workflow-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

1. Install (Claude Code Example)

claude mcp add spec-workflow-mcp -s user -- npx -y spec-workflow-mcp@latest

See [full installation guide](#installation) for other clients.

2. Start a New Project

"Help me use spec workflow to create a user authentication system"

3. Continue Existing Project

"Use spec workflow to check ./my-project"

The AI will automatically detect project status and continue from where it left off.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 304 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Spec Workflow MCP
  2. [![npm version](https://img.shields.io/npm/v/spec-workflow-mcp.svg)](https://www.npmjs.com/package/spec-workflow-mcp)
  3. [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
  4. [![MCP](https://img.shields.io/badge/MCP-Compatible-blue)](https://modelcontextprotocol.com)
  5. [English](README.md) | [简体中文](README-zh.md)
  6. Guide AI to systematically complete software development through a structured **Requirements → Design → Tasks** workflow, ensuring code implementation stays aligned with business needs.
  7. ## Why Use It?
  8. ### ❌ Without Spec Workflow
  9. - AI jumps randomly between tasks, lacking systematic approach
  10. - Requirements disconnect from actual code implementation
  11. - Scattered documentation, difficult to track project progress
  12. - Missing design decision records
  13. ### ✅ With Spec Workflow
  14. - AI completes tasks sequentially, maintaining focus and context
  15. - Complete traceability from user stories to code implementation
  16. - Standardized document templates with automatic progress management
  17. - Each stage requires confirmation, ensuring correct direction
  18. - **Persistent progress**: Continue from where you left off with `check`, even in new conversations
  19. ## Recent Updates
  20. > **v1.0.7**
  21. > - 🎯 Improved reliability for most models to manage tasks with spec workflow
  22. >
  23. > **v1.0.6**
  24. > - ✨ Batch task completion: Complete multiple tasks at once for faster progress on large projects
  25. >
  26. > **v1.0.5**
  27. > - 🐛 Edge case fixes: Distinguish between "task not found" and "task already completed" to prevent workflow interruption
  28. >
  29. > **v1.0.4**
  30. > - ✅ Task management: Added task completion tracking for systematic project progression
  31. >
  32. > **v1.0.3**
  33. > - 🎉 Initial release: Core workflow framework for Requirements → Design → Tasks
  34. ## Quick Start
  35. ### 1. Install (Claude Code Example)
  36. ```bash
  37. claude mcp add spec-workflow-mcp -s user -- npx -y spec-workflow-mcp@latest
  38. ```
  39. See [full installation guide](#installation) for other clients.
  40. ### 2. Start a New Project
  41. ```
  42. "Help me use spec workflow to create a user authentication system"
  43. ```
  44. ### 3. Continue Existing Project
  45. ```
  46. "Use spec workflow to check ./my-project"
  47. ```
  48. The AI will automatically detect project status and continue from where it left off.
  49. ## Workflow Example
  50. ### 1. You describe requirements
  51. ```
  52. You: "I need to build a user authentication system"
  53. ```
  54. ### 2. AI creates structured documents
  55. ```
  56. AI: "I'll help you create spec workflow for user authentication..."
  57. 📝 requirements.md - User stories and functional requirements
  58. 🎨 design.md - Technical architecture and design decisions
  59. ✅ tasks.md - Concrete implementation task list
  60. ```
  61. ### 3. Review and implement step by step
  62. After each stage, the AI requests your confirmation before proceeding, ensuring the project stays on the right track.
  63. ## Document Organization
  64. ### Basic Structure
  65. ```
  66. my-project/specs/
  67. ├── requirements.md # Requirements: user stories, functional specs
  68. ├── design.md # Design: architecture, APIs, data models
  69. ├── tasks.md # Tasks: numbered implementation steps
  70. └── .workflow-confirmations.json # Status: automatic progress tracking
  71. ```
  72. ### Multi-module Projects
  73. ```
  74. my-project/specs/
  75. ├── user-authentication/ # Auth module
  76. ├── payment-system/ # Payment module
  77. └── notification-service/ # Notification module
  78. ```
  79. You can specify any directory: `"Use spec workflow to create auth docs in ./src/features/auth"`
  80. ## AI Usage Guide
  81. ### 🤖 Make AI Use This Tool Better
  82. **Strongly recommended** to add the following prompt to your AI assistant configuration. Without it, AI may:
  83. - ❌ Not know when to invoke Spec Workflow
  84. - ❌ Forget to manage task progress, causing disorganized work
  85. - ❌ Not utilize Spec Workflow for systematic documentation
  86. - ❌ Unable to continuously track project status
  87. With this configuration, AI will intelligently use Spec Workflow to manage the entire development process.
  88. > **Configuration Note**: Please modify the following based on your needs:
  89. > 1. Change `./specs` to your preferred documentation directory path
  90. > 2. Change "English" to your preferred documentation language (e.g., "Chinese")
  91. ```
  92. # Spec Workflow Usage Guidelines
  93. ## 1. Check Project Progress
  94. When user mentions continuing previous project or is unsure about current progress, proactively use:
  95. specs-workflow tool with action.type="check" and path="./specs"
  96. ## 2. Documentation Language
  97. All spec workflow documents should be written in English consistently, including all content in requirements, design, and task documents.
  98. ## 3. Documentation Directory
  99. All spec workflow documents should be placed in ./specs directory to maintain consistent project documentation organization.
  100. ## 4. Task Management
  101. Always use the following to manage task progress:
  102. specs-workflow tool with action.type="complete_task" and taskNumber="current task number"
  103. Follow the workflow guidance to continue working until all tasks are completed.
  104. ## 5. Best Practices
  105. - Proactive progress check: When user says "continue from last time", first use check to see current status
  106. - Language consistency: Use the same language throughout all project documents
  107. - Flexible structure: Choose single-module or multi-module organization based on project scale
  108. - Task granularity: Each task should be completable within 1-2 hours
  109. ```
  110. ## Installation
  111. <details>
  112. <summary>📦 Installation Instructions</summary>
  113. ### Requirements
  114. - Node.js ≥ v18.0.0
  115. - npm or yarn
  116. - Claude Desktop or any MCP-compatible client
  117. ### Install in Different MCP Clients
  118. #### Claude Code (Recommended)
  119. Use the Claude CLI to add the MCP server:
  120. ```bash
  121. claude mcp add spec-workflow-mcp -s user -- npx -y spec-workflow-mcp@latest
  122. ```
  123. #### Claude Desktop
  124. Add to your Claude Desktop configuration:
  125. - macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
  126. - Windows: `%APPDATA%/Claude/claude_desktop_config.json`
  127. - Linux: `~/.config/Claude/claude_desktop_config.json`
  128. ```json
  129. {
  130. "mcpServers": {
  131. "spec-workflow": {
  132. "command": "npx",
  133. "args": ["-y", "spec-workflow-mcp@latest"]
  134. }
  135. }
  136. }
  137. ```
  138. #### Cursor
  139. Add to your Cursor configuration (`~/.cursor/config.json`):
  140. ```json
  141. {
  142. "mcpServers": {
  143. "spec-workflow": {
  144. "command": "npx",
  145. "args": ["-y", "spec-workflow-mcp@latest"]
  146. }
  147. }
  148. }
  149. ```
  150. #### Cline
  151. Use Cline's MCP server management UI to add the server:
  152. 1. Open VS Code with Cline extension
  153. 2. Open Cline settings (gear icon)
  154. 3. Navigate to MCP Servers section
  155. 4. Add new server with:
  156. - Command: `npx`
  157. - Arguments: `-y spec-workflow-mcp@latest`
  158. #### Windsurf (Codeium)
  159. Add to your Windsurf configuration (`~/.codeium/windsurf/mcp_config.json`):
  160. ```json
  161. {
  162. "mcpServers": {
  163. "spec-workflow": {
  164. "command": "npx",
  165. "args": ["-y", "spec-workflow-mcp@latest"],
  166. "env": {},
  167. "autoApprove": [],
  168. "disabled": false,
  169. "timeout": 60,
  170. "transportType": "stdio"
  171. }
  172. }
  173. }
  174. ```
  175. #### VS Code (with MCP extension)
  176. Add to your VS Code settings (`settings.json`):
  177. ```json
  178. {
  179. "mcp.servers": {
  180. "spec-workflow": {
  181. "command": "npx",
  182. "args": ["-y", "spec-workflow-mcp@latest"]
  183. }
  184. }
  185. }
  186. ```
  187. #### Zed
  188. Add to your Zed configuration (`~/.config/zed/settings.json`):
  189. ```json
  190. {
  191. "assistant": {
  192. "version": "2",
  193. "mcp": {
  194. "servers": {
  195. "spec-workflow": {
  196. "command": "npx",
  197. "args": ["-y", "spec-workflow-mcp@latest"]
  198. }
  199. }
  200. }
  201. }
  202. }
  203. ```
  204. ### Install from Source
  205. ```bash
  206. git clone https://github.com/kingkongshot/specs-mcp.git
  207. cd specs-mcp
  208. npm install
  209. npm run build
  210. ```
  211. Then add to Claude Desktop configuration:
  212. ```json
  213. {
  214. "mcpServers": {
  215. "spec-workflow": {
  216. "command": "node",
  217. "args": ["/absolute/path/to/specs-mcp/dist/index.js"]
  218. }
  219. }
  220. }
  221. ```
  222. </details>
  223. ## Links
  224. - [GitHub Repository](https://github.com/kingkongshot/specs-mcp)
  225. - [NPM Package](https://www.npmjs.com/package/spec-workflow-mcp)
  226. - [Report Issues](https://github.com/kingkongshot/specs-mcp/issues)
  227. ## License
  228. MIT License
  229. ---
  230. <a href="https://glama.ai/mcp/servers/@kingkongshot/specs-workflow-mcp">
  231. <img width="380" height="200" src="https://glama.ai/mcp/servers/@kingkongshot/specs-workflow-mcp/badge" alt="Spec Workflow MCP server" />
  232. </a>

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.