Flight505 MCP Dincoder

What flight505-mcp_dincoder MCP server does

flight505-mcp_dincoder MCP server applies a specification-driven workflow to software projects through the Model Context Protocol. Instead of moving directly from a prompt to generated code, it helps an AI coding assistant create and maintain structured project artifacts.

The workflow starts with a project constitution when needed, then moves through a feature specification, an implementation plan, and an ordered task list. Generated materials can include requirements, user stories, acceptance criteria, data models, API contracts, test scenarios, technical research, and implementation tasks. Feature directories are numbered automatically under specs/, such as specs/001-feature-name/.

How it works

The server exposes seven MCP prompts for common activities: starting a project, creating a specification, generating a plan, creating tasks, reviewing progress, validating a specification, and finding the next actionable tasks. These prompts are workflow templates that an MCP client can discover and invoke; they are not slash commands that must be entered directly.

The process separates product requirements from implementation choices. A specification describes what users need and why. A plan records architecture and technology decisions, including their relationship to the requirements. Task generation then converts the plan and contracts into numbered work items, including dependency ordering and parallelizable tasks where applicable.

DinCoder also provides constitution_create for project-wide principles, constraints, and preferences. Its clarification commands—clarify_add, clarify_resolve, and clarify_list—track unresolved questions with identifiers such as CLARIFY-001, along with resolution rationale and an audit trail.

Setup and configuration

Install with Smithery using npx -y @smithery/cli install @flight505/mcp_dincoder, or add it to Claude Code and VS Code with claude mcp add dincoder -- npx -y mcp-dincoder@latest. Other MCP clients can use a global installation through npm install -g mcp-dincoder@latest.

The runtime requires Node.js 20 or newer and npm or pnpm. Launch the MCP client from the repository root so generated files are written to the intended project. The flight505-mcp_dincoder MCP server expects the client to provide the active workspace path automatically. Cursor, Claude Code, and Codex do this per request. Claude Desktop does not, so calls from that client should provide workspacePath manually.

Tools and capabilities

• Seven discoverable workflow prompts for project and feature planning.
• Project constitution creation with constitution_create.
• Clarification creation, resolution, and listing.
• Automatic feature numbering and structured files under specs/.
• Specifications containing user stories, acceptance criteria, and clarification markers.
• Plans with data models, API contracts, test scenarios, and technology rationale.
• Ordered task lists with dependency information and parallel-work markers.

Limitations and notes

The flight505-mcp_dincoder MCP server writes into the current working directory, so an incorrectly launched client can place artifacts in the wrong location. Claude Desktop requires explicit workspace-path handling for each call according to the README. The documented setup does not list environment variables, and the provided material does not specify a license.

The repository describes a legacy .dincoder/ directory for backward compatibility, while new project artifacts use the specs/ layout. The server organizes planning and specification artifacts; the provided material does not claim that it implements the generated application code itself.