ai.smithery/flight505-mcp_dincoder

Install

Config snippet generator goes here (5 client tabs)

README

<div align="center">
  <img width="320" alt="Image@0 5x" src="https://github.com/user-attachments/assets/defd2ef0-5804-431c-8549-618eb3434aee" />
</div>

[![smithery badge](https://smithery.ai/badge/@flight505/mcp_dincoder)](https://smithery.ai/server/@flight505/mcp_dincoder)

**D**riven **I**ntent **N**egotiation — **C**ontract-**O**riented **D**eterministic **E**xecutable **R**untime

> *The MCP implementation of GitHub's Spec Kit methodology — transforming specifications into executable artifacts*

---

## Table of Contents

- [What is DinCoder?](#-what-is-dincoder)
- [Installation](#-installation)
- [Quickstart](#-quickstart)
- [MCP Prompts (AI Workflow Orchestration)](#-mcp-prompts-ai-workflow-orchestration)
- [Complete Workflow](#-complete-workflow-guide)
- [Available Tools](#-available-tools)
- [Examples](#-examples)
- [Why Spec-Driven Development?](#-why-spec-driven-development)
- [Roadmap](#-roadmap)
- [Contributing](#-contributing)

---

## 🎯 What is DinCoder?

**An official Model Context Protocol server implementing GitHub's Spec-Driven Development (SDD) methodology**

DinCoder brings the power of [GitHub Spec Kit](https://github.com/github/spec-kit) to any AI coding agent through the Model Context Protocol. It transforms the traditional "prompt-then-code-dump" workflow into a systematic, specification-driven process where **specifications don't serve code—code serves specifications**.

### What's New in v0.4.0 (Integration & Discovery Update)

#### 🎯 MCP Prompts - AI Workflow Orchestration ✨

- **7 workflow prompts** that guide AI agents through complex tasks
- **Automatic discovery**: AI agents find and use prompts programmatically
- **Built-in guidance**: Each prompt includes comprehensive workflow instructions
- **Works everywhere**: Claude Code, VS Code Copilot, OpenAI Codex, Cursor
- **Natural language**: Just describe what you want - AI uses appropriate prompts automatically

**Available Prompts:**
- `start_project` - Initialize new spec-driven project
- `create_spec` - Create feature specification
- `generate_plan` - Generate implementation plan
- `create_tasks` - Break down into actionable tasks
- `review_progress` - Generate progress report
- `validate_spec` - Check specification quality
- `next_tasks` - Show actionable tasks

**Note:** These are NOT slash commands you type. They're workflow templates that your AI agent uses automatically when you describe your goals!

#### 🧬 Constitution Tool - Define Your Project's DNA

- **New command:** `constitution_create`
- Set project-wide principles, constraints, and preferences
- Ensures consistency across all AI-generated code

#### ❓ Clarification Tracking - Systematic Q&A Management

- **New commands:** `clarify_add`, `clarify_resolve`, `clarify_list`
- Track ambiguities with unique IDs (CLARIFY-001, CLARIFY-002, etc.)
- Resolve uncertainties with rationale and audit trail

---

## 📦 Installation

> **🎯 Quick Decision Guide:**
> - **Using Claude Code?** → Install the [Plugin](#-claude-code-plugin-recommended-for-claude-code) (easier, includes slash commands & agents)
> - **Using VS Code/Codex/Cursor?** → Install [MCP Server Only](#installing-via-smithery) (plugins not supported)
>
> ⚠️ **Don't install both!** The plugin automatically installs the MCP server - installing both may cause conflicts.

### Prerequisites

- Node.js >= 20.0.0
- npm or pnpm
- An MCP-compatible coding assistant with automatic workspace binding (Cursor, Claude Code, Codex, etc.)

### Installing via Smithery

To install DinCoder automatically via [Smithery](https://smithery.ai/server/@flight505/mcp_dincoder):

```bash
npx -y @smithery/cli install @flight505/mcp_dincoder
```

### Claude Code / VS Code Users

```bash
claude mcp add dincoder -- npx -y mcp-dincoder@latest
```

### Cursor

Configure the MCP server inside Cursor's MCP settings; once you select a project, Cursor injects the workspace path automatically.

### Other MCP Clients

Install globally:
```bash
npm install -g mcp-dincoder@latest
```

> **Recommended clients:** DinCoder expects the MCP client to bind the active project directory automatically so generated specs, plans, and tasks land in the repo you are working on. Cursor, Claude Code, and Codex do this for every request. Claude Desktop's chat UI does not, so commands default to the server's own install directory; only use Claude Desktop if you plan to pass `workspacePath` manually on each call.

### 📁 Where Files Are Created

**Important:** DinCoder creates all files in your **current working directory** (where you run your AI agent from).

```bash
your-project/
├── specs/                    # Created automatically
│   ├── 001-feature-name/    # Feature directory (auto-numbered)
│   │   ├── constitution.md  # Project principles (optional, recommended first step)
│   │   ├── spec.md          # Requirements & user stories
│   │   ├── plan.md          # Technical implementation plan
│   │   ├── tasks.md         # Executable task list
│   │   ├── re