dmatta22201/spec-driven-development-mcp-server

Spec-Driven Development MCP Server

A Model Context Protocol (MCP) server for spec-driven development that integrates with Amazon Q CLI. Provides LLM-powered tools to generate requirements, design, and task documents from conversations or product descriptions.

Components

1. MCP Server (mcp-server/)

Local Model Context Protocol server with four specialized tools for document generation and web content fetching.

Tools:

• generate_requirements - Generate requirements.md from conversation/description
• generate_design - Generate design.md from requirements document
• generate_tasks - Generate tasks.md from requirements and design documents
• query_web - Fetch and parse web page content

2. Q CLI Integration (q-cli-integration/)

Configuration and setup scripts for integrating the MCP server with AWS Q CLI.

Setup

1. Install MCP Server Dependencies:

   cd mcp-server
   npm install
   

2. Setup Q CLI Integration:

   cd q-cli-integration
   chmod +x setup.sh
   ./setup.sh
   

Usage

Generate Requirements Document

q chat "Generate requirements for a todo application that allows users to create, edit, delete, and organize tasks by categories with due dates"

Generate Design Document

q chat "Generate a design document from the requirements.md file located at ./requirements.md for project TodoApp"

Generate Tasks Document

q chat "Generate tasks from requirements.md and design.md files for project TodoApp"

Query Web Content

q chat "Use the query_web tool to fetch content from https://example.com"

LLM-Powered Features

All document generation tools use intelligent LLM analysis to:

• Ask follow-up questions when critical information is missing
• Make informed decisions based on project context
• Generate specific content tailored to actual requirements
• Follow best practices for software development documentation

Smart Follow-up Questions

The tools will ask clarifying questions such as:

• "Should this be a web application, desktop application, or mobile app?"
• "What level of security is required?"
• "How many concurrent users should the system support?"
• "What technologies or frameworks do you prefer?"

Generated Documents

Requirements Document

• Project overview and executive summary
• Functional requirements with acceptance criteria
• Non-functional requirements (performance, security, scalability)
• User stories in proper format
• Constraints and dependencies
• Success metrics

Design Document

• System architecture and component design
• Technology stack recommendations
• API design with specific endpoints
• Security and performance considerations
• Deployment strategy
• Risk assessment

Tasks Document

• Complete TDD-based task breakdown
• Technology-specific setup tasks
• Feature implementation with RED-GREEN-REFACTOR cycles
• Integration tasks for third-party services
• Testing and deployment phases
• Project timeline and estimates

File Structure

spec-driven-development/
├── mcp-server/
│   ├── package.json
│   └── src/
│       ├── index.js
│       └── tools/
│           ├── queryWeb.js
│           ├── generateRequirements.js
│           ├── generateDesign.js
│           └── generateTasks.js
├── q-cli-integration/
│   ├── mcp.json
│   └── setup.sh
├── references/
│   └── templates/
│       ├── requirements.md
│       ├── design.md
│       └── tasks.md
├── python-best-practices.md
├── nodejs-best-practices.md
└── README.md

Requirements

• Node.js 22.x or higher
• Amazon Q CLI installed and configured
• Linux/macOS (Windows support not tested)