DinCoder

DinCoder is an MCP server that implements GitHub's Spec-Driven Development methodology, transforming AI coding workflows from ad-hoc prompting into systematic, specification-driven processes. It brings GitHub Spec Kit capabilities to AI coding agents, ensuring code serves specifications rather than the other way around. Key capabilities of DinCoder: - AI workflow orchestration through MCP prompts with seven built-in workflows for project initialization, spec creation, implementation planning, task breakdown, and progress review - Specification management tools for creating, validating, and managing feature specifications as the foundation of development - Project constitution tool for defining project-wide principles, constraints, and coding preferences to ensure consistency across AI-generated code - Clarification tracking with systematic Q&A management using unique IDs (CLARIFY-001, etc.) for tracking ambiguities and resolutions with full audit trails - Task management for breaking specifications into actionable tasks and tracking implementation progress

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

Driven Intent Negotiation — Contract-Oriented Deterministic Executable Runtime

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

---

Table of Contents

---

🎯 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 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 ✨

Available Prompts:

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

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

---

📦 Installation

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

Prerequisites

Installing via Smithery

To install DinCoder automatically via Smithery:

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

Claude Code / VS Code Users

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:

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 │ │ ├── research