[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-73670":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":23,"hasPages":23,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":26,"readmeContent":27,"aiSummary":28,"trendingCount":16,"starSnapshotCount":16,"syncStatus":29,"lastSyncTime":30,"discoverSource":31},73670,"spec-workflow-mcp","Pimzino\u002Fspec-workflow-mcp","Pimzino","A Model Context Protocol (MCP) server that provides structured spec-driven development workflow tools for AI-assisted software development, featuring a real-time web dashboard and VSCode extension for monitoring and managing your project's progress directly in your development environment.","",null,"TypeScript",4222,348,33,1,0,5,9,52,15,79.33,"GNU General Public License v3.0",false,"main",[],"2026-06-12 04:01:10","# Spec Workflow MCP\n\n[![npm version](https:\u002F\u002Fimg.shields.io\u002Fnpm\u002Fv\u002F@pimzino\u002Fspec-workflow-mcp)](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@pimzino\u002Fspec-workflow-mcp)\n[![VSCode Extension](https:\u002F\u002Fvsmarketplacebadges.dev\u002Fversion-short\u002FPimzino.spec-workflow-mcp.svg)](https:\u002F\u002Fmarketplace.visualstudio.com\u002Fitems?itemName=Pimzino.spec-workflow-mcp)\n\nA Model Context Protocol (MCP) server for structured spec-driven development with real-time dashboard and VSCode extension.\n\n## ☕ Support This Project\n\n\u003Ca href=\"https:\u002F\u002Fbuymeacoffee.com\u002FPimzino\" target=\"_blank\">\u003Cimg src=\"https:\u002F\u002Fcdn.buymeacoffee.com\u002Fbuttons\u002Fv2\u002Fdefault-yellow.png\" alt=\"Buy Me A Coffee\" style=\"height: 60px !important;width: 217px !important;\" >\u003C\u002Fa>\n\n## 📺 Showcase\n\n### 🔄 Approval System in Action\n\u003Ca href=\"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=C-uEa3mfxd0\" target=\"_blank\">\n  \u003Cimg src=\"https:\u002F\u002Fimg.youtube.com\u002Fvi\u002FC-uEa3mfxd0\u002Fmaxresdefault.jpg\" alt=\"Approval System Demo\" width=\"600\">\n\u003C\u002Fa>\n\n*See how the approval system works: create documents, request approval through the dashboard, provide feedback, and track revisions.*\n\n### 📊 Dashboard & Spec Management\n\u003Ca href=\"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=g9qfvjLUWf8\" target=\"_blank\">\n  \u003Cimg src=\"https:\u002F\u002Fimg.youtube.com\u002Fvi\u002Fg9qfvjLUWf8\u002Fmaxresdefault.jpg\" alt=\"Dashboard Demo\" width=\"600\">\n\u003C\u002Fa>\n\n*Explore the real-time dashboard: view specs, track progress, navigate documents, and monitor your development workflow.*\n\n## ✨ Key Features\n\n- **Structured Development Workflow** - Sequential spec creation (Requirements → Design → Tasks)\n- **Real-Time Web Dashboard** - Monitor specs, tasks, and progress with live updates\n- **VSCode Extension** - Integrated sidebar dashboard for VSCode users\n- **Approval Workflow** - Complete approval process with revisions\n- **Task Progress Tracking** - Visual progress bars and detailed status\n- **Implementation Logs** - Searchable logs of all task implementations with code statistics\n- **Multi-Language Support** - Available in 11 languages\n\n## 🌍 Supported Languages\n\n🇺🇸 English • 🇯🇵 日本語 • 🇨🇳 中文 • 🇪🇸 Español • 🇧🇷 Português • 🇩🇪 Deutsch • 🇫🇷 Français • 🇷🇺 Русский • 🇮🇹 Italiano • 🇰🇷 한국어 • 🇸🇦 العربية\n\n**📖 Documentation in your language:**\n\n[English](README.md) | [日本語](README.ja.md) | [中文](README.zh.md) | [Español](README.es.md) | [Português](README.pt.md) | [Deutsch](README.de.md) | [Français](README.fr.md) | [Русский](README.ru.md) | [Italiano](README.it.md) | [한국어](README.ko.md) | [العربية](README.ar.md)\n\n## 🚀 Quick Start\n\n### Step 1: Add to your AI tool\n\nAdd to your MCP configuration (see client-specific setup below):\n\n```json\n{\n  \"mcpServers\": {\n    \"spec-workflow\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@pimzino\u002Fspec-workflow-mcp@latest\", \"\u002Fpath\u002Fto\u002Fyour\u002Fproject\"]\n    }\n  }\n}\n```\n\n### Step 2: Choose your interface\n\n**Option A: Web Dashboard** (Required for CLI users)\nStart the dashboard (runs on port 5000 by default):\n```bash\nnpx -y @pimzino\u002Fspec-workflow-mcp@latest --dashboard\n```\n\nThe dashboard will be accessible at: http:\u002F\u002Flocalhost:5000\n\n> **Note:** Only one dashboard instance is needed. All your projects will connect to the same dashboard.\n\n**Option B: VSCode Extension** (Recommended for VSCode users)\n\nInstall [Spec Workflow MCP Extension](https:\u002F\u002Fmarketplace.visualstudio.com\u002Fitems?itemName=Pimzino.spec-workflow-mcp) from the VSCode marketplace.\n\n## 📝 How to Use\n\nSimply mention spec-workflow in your conversation:\n\n- **\"Create a spec for user authentication\"** - Creates complete spec workflow\n- **\"List my specs\"** - Shows all specs and their status\n- **\"Execute task 1.2 in spec user-auth\"** - Runs a specific task\n\n[See more examples →](docs\u002FPROMPTING-GUIDE.md)\n\n## 🔧 MCP Client Setup\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Augment Code\u003C\u002Fstrong>\u003C\u002Fsummary>\n\nConfigure in your Augment settings:\n```json\n{\n  \"mcpServers\": {\n    \"spec-workflow\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@pimzino\u002Fspec-workflow-mcp@latest\", \"\u002Fpath\u002Fto\u002Fyour\u002Fproject\"]\n    }\n  }\n}\n```\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Claude Code CLI\u003C\u002Fstrong>\u003C\u002Fsummary>\n\nAdd to your MCP configuration:\n```bash\nclaude mcp add spec-workflow npx @pimzino\u002Fspec-workflow-mcp@latest -- \u002Fpath\u002Fto\u002Fyour\u002Fproject\n```\n\n**Important Notes:**\n- The `-y` flag bypasses npm prompts for smoother installation\n- The `--` separator ensures the path is passed to the spec-workflow script, not to npx\n- Replace `\u002Fpath\u002Fto\u002Fyour\u002Fproject` with your actual project directory path\n\n**Alternative for Windows (if the above doesn't work):**\n```bash\nclaude mcp add spec-workflow cmd.exe \u002Fc \"npx @pimzino\u002Fspec-workflow-mcp@latest \u002Fpath\u002Fto\u002Fyour\u002Fproject\"\n```\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Claude Desktop\u003C\u002Fstrong>\u003C\u002Fsummary>\n\nAdd to `claude_desktop_config.json`:\n```json\n{\n  \"mcpServers\": {\n    \"spec-workflow\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@pimzino\u002Fspec-workflow-mcp@latest\", \"\u002Fpath\u002Fto\u002Fyour\u002Fproject\"]\n    }\n  }\n}\n```\n\n> **Important:** Run the dashboard separately with `--dashboard` before starting the MCP server.\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Cline\u002FClaude Dev\u003C\u002Fstrong>\u003C\u002Fsummary>\n\nAdd to your MCP server configuration:\n```json\n{\n  \"mcpServers\": {\n    \"spec-workflow\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@pimzino\u002Fspec-workflow-mcp@latest\", \"\u002Fpath\u002Fto\u002Fyour\u002Fproject\"]\n    }\n  }\n}\n```\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Continue IDE Extension\u003C\u002Fstrong>\u003C\u002Fsummary>\n\nAdd to your Continue configuration:\n```json\n{\n  \"mcpServers\": {\n    \"spec-workflow\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@pimzino\u002Fspec-workflow-mcp@latest\", \"\u002Fpath\u002Fto\u002Fyour\u002Fproject\"]\n    }\n  }\n}\n```\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Cursor IDE\u003C\u002Fstrong>\u003C\u002Fsummary>\n\nAdd to your Cursor settings (`settings.json`):\n```json\n{\n  \"mcpServers\": {\n    \"spec-workflow\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@pimzino\u002Fspec-workflow-mcp@latest\", \"\u002Fpath\u002Fto\u002Fyour\u002Fproject\"]\n    }\n  }\n}\n```\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>OpenCode\u003C\u002Fstrong>\u003C\u002Fsummary>\n\nAdd to your `opencode.json` configuration file:\n```json\n{\n  \"$schema\": \"https:\u002F\u002Fopencode.ai\u002Fconfig.json\",\n  \"mcp\": {\n    \"spec-workflow\": {\n      \"type\": \"local\",\n      \"command\": [\"npx\", \"-y\", \"@pimzino\u002Fspec-workflow-mcp@latest\", \"\u002Fpath\u002Fto\u002Fyour\u002Fproject\"],\n      \"enabled\": true\n    }\n  }\n}\n```\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Windsurf\u003C\u002Fstrong>\u003C\u002Fsummary>\n\nAdd to your `~\u002F.codeium\u002Fwindsurf\u002Fmcp_config.json` configuration file:\n```json\n{\n  \"mcpServers\": {\n    \"spec-workflow\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@pimzino\u002Fspec-workflow-mcp@latest\", \"\u002Fpath\u002Fto\u002Fyour\u002Fproject\"]\n    }\n  }\n}\n```\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Codex\u003C\u002Fstrong>\u003C\u002Fsummary>\n\nAdd to your `~\u002F.codex\u002Fconfig.toml` configuration file:\n```toml\n[mcp_servers.spec-workflow]\ncommand = \"npx\"\nargs = [\"-y\", \"@pimzino\u002Fspec-workflow-mcp@latest\", \"\u002Fpath\u002Fto\u002Fyour\u002Fproject\"]\n```\n\u003C\u002Fdetails>\n\n## 🐳 Docker Deployment\n\nRun the dashboard in a Docker container for isolated deployment:\n\n```bash\n# Using Docker Compose (recommended)\ncd containers\ndocker-compose up --build\n\n# Or using Docker CLI\ndocker build -f containers\u002FDockerfile -t spec-workflow-mcp .\ndocker run -p 5000:5000 -v \".\u002Fworkspace\u002F.spec-workflow:\u002Fworkspace\u002F.spec-workflow:rw\" spec-workflow-mcp\n```\n\nThe dashboard will be available at: http:\u002F\u002Flocalhost:5000\n\n[See Docker setup guide →](containers\u002FREADME.md)\n\n## 🔒 Security\n\nSpec-Workflow MCP includes enterprise-grade security features suitable for corporate environments:\n\n### ✅ Implemented Security Controls\n\n| Feature | Description |\n|---------|-------------|\n| **Localhost Binding** | Binds to `127.0.0.1` by default, preventing network exposure |\n| **Rate Limiting** | 120 requests\u002Fminute per client with automatic cleanup |\n| **Audit Logging** | Structured JSON logs with timestamp, actor, action, and result |\n| **Security Headers** | X-Content-Type-Options, X-Frame-Options, X-XSS-Protection, CSP, Referrer-Policy |\n| **CORS Protection** | Restricted to localhost origins by default |\n| **Docker Hardening** | Non-root user, read-only filesystem, dropped capabilities, resource limits |\n\n### ⚠️ Not Yet Implemented\n\n| Feature | Workaround |\n|---------|------------|\n| **HTTPS\u002FTLS** | Use a reverse proxy (nginx, Apache) with TLS certificates |\n| **User Authentication** | Use a reverse proxy with Basic Auth or OAuth2 Proxy for SSO |\n\n### For External\u002FNetwork Access\n\nIf you need to expose the dashboard beyond localhost, we recommend:\n\n1. **Keep dashboard on localhost** (`127.0.0.1`)\n2. **Use nginx or Apache** as a reverse proxy with:\n   - TLS\u002FHTTPS termination\n   - Basic authentication or OAuth2\n3. **Configure firewall rules** to restrict access\n\n```nginx\n# Example nginx reverse proxy with auth\nserver {\n    listen 443 ssl;\n    server_name dashboard.example.com;\n    \n    ssl_certificate \u002Fpath\u002Fto\u002Fcert.pem;\n    ssl_certificate_key \u002Fpath\u002Fto\u002Fkey.pem;\n    \n    auth_basic \"Dashboard Access\";\n    auth_basic_user_file \u002Fetc\u002Fnginx\u002F.htpasswd;\n    \n    location \u002F {\n        proxy_pass http:\u002F\u002F127.0.0.1:5000;\n        proxy_http_version 1.1;\n        proxy_set_header Upgrade $http_upgrade;\n        proxy_set_header Connection \"upgrade\";\n    }\n}\n```\n\n[See Docker security guide →](containers\u002FREADME.md#security-configuration)\n\n## 🔒 Sandboxed Environments\n\nFor sandboxed environments (e.g., Codex CLI with `sandbox_mode=workspace-write`) where `$HOME` is read-only, use the `SPEC_WORKFLOW_HOME` environment variable to redirect global state files to a writable location:\n\n```bash\nSPEC_WORKFLOW_HOME=\u002Fworkspace\u002F.spec-workflow-mcp npx -y @pimzino\u002Fspec-workflow-mcp@latest \u002Fworkspace\n```\n\n[See Configuration Guide →](docs\u002FCONFIGURATION.md#environment-variables)\n\n## 📚 Documentation\n\n- [Configuration Guide](docs\u002FCONFIGURATION.md) - Command-line options, config files\n- [User Guide](docs\u002FUSER-GUIDE.md) - Comprehensive usage examples\n- [Workflow Process](docs\u002FWORKFLOW.md) - Development workflow and best practices\n- [Interfaces Guide](docs\u002FINTERFACES.md) - Dashboard and VSCode extension details\n- [Prompting Guide](docs\u002FPROMPTING-GUIDE.md) - Advanced prompting examples\n- [Tools Reference](docs\u002FTOOLS-REFERENCE.md) - Complete tools documentation\n- [Development](docs\u002FDEVELOPMENT.md) - Contributing and development setup\n- [Troubleshooting](docs\u002FTROUBLESHOOTING.md) - Common issues and solutions\n\n## 📁 Project Structure\n\n```\nyour-project\u002F\n  .spec-workflow\u002F\n    approvals\u002F\n    archive\u002F\n    specs\u002F\n    steering\u002F\n    templates\u002F\n    user-templates\u002F\n    config.example.toml\n```\n\n## 🛠️ Development\n\n```bash\n# Install dependencies\nnpm install\n\n# Build the project\nnpm run build\n\n# Run in development mode\nnpm run dev\n```\n\n[See development guide →](docs\u002FDEVELOPMENT.md)\n\n## 📄 License\n\nGPL-3.0\n\n## ⭐ Star History\n\n\u003Ca href=\"https:\u002F\u002Fwww.star-history.com\u002F#Pimzino\u002Fspec-workflow-mcp&Date\">\n \u003Cpicture>\n   \u003Csource media=\"(prefers-color-scheme: dark)\" srcset=\"https:\u002F\u002Fapi.star-history.com\u002Fsvg?repos=Pimzino\u002Fspec-workflow-mcp&type=Date&theme=dark\" \u002F>\n   \u003Csource media=\"(prefers-color-scheme: light)\" srcset=\"https:\u002F\u002Fapi.star-history.com\u002Fsvg?repos=Pimzino\u002Fspec-workflow-mcp&type=Date\" \u002F>\n   \u003Cimg alt=\"Star History Chart\" src=\"https:\u002F\u002Fapi.star-history.com\u002Fsvg?repos=Pimzino\u002Fspec-workflow-mcp&type=Date\" \u002F>\n \u003C\u002Fpicture>\n\u003C\u002Fa>","Pimzino\u002Fspec-workflow-mcp 是一个用于结构化规格驱动开发的 Model Context Protocol (MCP) 服务器，提供了实时Web仪表盘和VSCode扩展来监控和管理项目进度。其核心功能包括结构化的开发工作流程、实时更新的Web仪表盘以及与VSCode集成的侧边栏仪表盘，支持需求到设计再到任务的顺序创建，并具备审批流程、任务进度跟踪及多语言支持等特性。此项目适用于需要规范软件开发过程并希望在开发环境中直接管理和监控项目进展的团队。",2,"2026-06-11 03:46:50","high_star"]