Server data from the Official MCP Registry
Transform project ideas into paint-by-numbers development plans with phases, tasks, and subtasks.
Transform project ideas into paint-by-numbers development plans with phases, tasks, and subtasks.
Remote endpoints: streamable-http: https://devplan-mcp-server.mike-c63.workers.dev/mcp
DevPlan MCP Server is a development planning tool with reasonable security posture. The codebase demonstrates good software engineering practices with no evidence of malicious patterns, credential exfiltration, or dangerous operations. Minor findings around input validation and error handling are typical code quality issues that do not constitute security vulnerabilities. Permissions align well with the server's purpose as a planning and code generation tool. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 1 high severity).
4 files analyzed · 8 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Available as Local & Remote
This plugin can run on your machine or connect to a hosted endpoint. during install.
From the project's GitHub README.
Transform ideas into executable development plans — an MCP server that brings the ClaudeCode-DevPlanBuilder methodology to Claude Code.
The Problem: AI coding assistants often lose context, skip steps, or produce inconsistent code across sessions.
The Solution: DevPlan creates detailed, agent-executable development plans with built-in validation, lessons learned, and inline git workflows.
| Feature | Description |
|---|---|
| Agent-Executable Plans | Plans so detailed that any LLM coding agent can execute them mechanically |
| Built-in Validation | Validates plans are complete before execution begins |
| Real-Time Progress Tracking | Integrates with Claude Code's Task tools for live visibility |
| Lessons Learned | Captures issues from verification and injects them into future plans |
| Issue Remediation | Converts GitHub issues directly into remediation tasks |
| Executor & Verifier Agents | Auto-generates specialized agents with task tracking built-in |
claude mcp add devplan --transport sse https://mcp.devplanmcp.store/sse --scope user
Or add to ~/.claude.json under the mcpServers key:
{
"mcpServers": {
"devplan": {
"type": "sse",
"url": "https://mcp.devplanmcp.store/sse"
}
}
}
If you already have DevPlan installed, remove from both scopes and re-add:
claude mcp remove devplan --scope project; claude mcp remove devplan --scope user; claude mcp add devplan --transport sse https://mcp.devplanmcp.store/sse --scope user
You: "Use devplan_start to help me build a CLI tool for managing dotfiles"
That's it. DevPlan will guide Claude through the entire process.
DevPlan uses a scaffold → enhance → validate workflow that ensures every plan is agent-executable before implementation begins.
flowchart LR
subgraph Planning["📋 Planning"]
A[Interview] --> B[Brief]
B --> C[Generate Scaffold]
end
subgraph Enhancement["✨ Enhancement"]
C --> D[Enhance with Code]
D --> E{Validate}
E -->|Fail| D
E -->|Pass| F[Ready]
end
subgraph Execution["⚡ Execution"]
F --> G[Agent Executes]
G --> H[Agent Verifies]
end
subgraph Learning["🧠 Learning"]
H -->|issues| I[Capture Lessons]
I -->|improve| C
end
style E fill:#fff3e0,stroke:#f57c00
style F fill:#c8e6c9,stroke:#2e7d32
style I fill:#e3f2fd,stroke:#1565c0
devplan_generate_plan creates foundation phases + a feature listdevplan_validate_plan checks the plan is agent-executableThe validation step checks that plans are truly executable:
# Example validation output
{
"valid": true,
"errors": [],
"warnings": [],
"stats": {
"subtasks": 5,
"codeBlocksChecked": 8,
"issuesFound": 0
}
}
Generated executor and verifier agents integrate with Claude Code's Task tools for live progress visibility:
# Example: Executor tracks subtasks
TaskCreate({ subject: "1.2.3: Implement auth middleware", activeForm: "Implementing auth middleware" })
TaskUpdate({ taskId: "...", status: "in_progress" })
# ... work happens ...
TaskUpdate({ taskId: "...", status: "completed" })
Both Task tools (real-time visibility) and DEVELOPMENT_PLAN.md (durable record) are updated — giving you the best of both worlds.
"Use devplan_start to help me build [your idea]"
# Get issue JSON
gh issue view 123 --json number,title,body,labels,comments,url > issue.json
# Then tell Claude:
"Use devplan_issue_to_task with this issue to create a remediation plan"
"Use devplan_progress_summary to show me where we are"
DevPlan generates plans and agent files for multiple AI coding tools and models. Use the target parameter to generate outputs for your preferred tool.
| Target | Tool | Agent File | Best For |
|---|---|---|---|
claude | Claude Code | CLAUDE.md | Claude Code IDE (default) |
cursor | Cursor IDE | .cursorrules | Cursor AI editor |
aider | Aider CLI | .aider.conf.yml | Terminal-based AI pair programming |
cline | VS Code Cline | .cline/instructions.md | VS Code extension |
windsurf | Windsurf IDE | .windsurf/rules.md | Codium's AI IDE |
generic | Any Model | AGENTS.md + files | Model-agnostic markdown format |
When generating plans or agent files, specify the target tool:
Generate plan for Cursor:
"Use devplan_generate_plan to create a plan, then I'll customize it for Cursor. Set target to 'cursor' for .cursorrules format"
Generate executor for Aider:
"Use devplan_generate_executor with target='aider' to create an Aider-compatible executor agent"
Generate generic agent files:
"Use devplan_generate_claude_md with target='generic' to create model-agnostic AGENTS.md files"
Each target has a dedicated adapter that transforms the DevPlan methodology into the appropriate format:
CLAUDE.md with executor/verifier agents in .claude/agents/.cursorrules with all guidance in one file (Cursor doesn't support separate agents).aider.conf.yml with architect mode instructions.cline/instructions.md with executor/verifier split.windsurf/rules.md with cascade-optimized formatAGENTS.md, EXECUTOR.md, and VERIFIER.md for any toolStart a new project for Cursor:
"Use devplan_start to help me build a CLI tool, then generate the plan with target='cursor' for Cursor IDE"
Add executor for specific target:
"I have a development plan. Use devplan_generate_executor with target='aider' to create the executor agent for Aider"
Compare adapter capabilities: See docs/ADAPTERS.md for a detailed comparison of each target's capabilities and limitations.
| Tool | Purpose |
|---|---|
devplan_start | Main entry point - guides Claude through the methodology |
devplan_interview_questions | Get questions to gather project requirements |
devplan_create_brief | Generate PROJECT_BRIEF.md |
devplan_parse_brief | Parse existing brief into structured data |
devplan_list_templates | List project templates (cli, web_app, api, library) |
| Tool | Purpose |
|---|---|
devplan_generate_plan | Generate DEVELOPMENT_PLAN.md scaffold with validation instructions |
devplan_generate_claude_md | Generate CLAUDE.md scaffold |
devplan_generate_executor | Generate executor agent with Task tool integration |
devplan_generate_verifier | Generate verifier agent with Task tool integration |
| Tool | Purpose |
|---|---|
devplan_validate_plan | Validate plan structure and agent-executability |
devplan_get_subtask | Get specific subtask details by ID |
devplan_update_progress | Mark subtasks complete with notes |
devplan_progress_summary | Get completion stats and next actions |
Feedback loop that captures issues from verification and incorporates them into future plans.
| Tool | Purpose |
|---|---|
devplan_add_lesson | Capture a lesson from verifier findings |
devplan_list_lessons | List accumulated lessons by severity |
devplan_archive_lesson | Archive old lessons without deleting them |
devplan_delete_lesson | Remove outdated or incorrect lessons |
devplan_extract_lessons_from_report | Auto-extract lessons from verification reports |
Convert GitHub issues into structured remediation tasks — perfect for bug fixes and post-release maintenance.
| Tool | Purpose |
|---|---|
devplan_parse_issue | Analyze a GitHub issue to extract requirements |
devplan_issue_to_task | Generate remediation task with subtasks from an issue |
| Tool | Purpose |
|---|---|
devplan_usage_stats | View usage distribution across users |
| Without DevPlan | With DevPlan |
|---|---|
| Context lost between sessions | Plans preserve full context |
| Inconsistent code quality | Executor agents follow exact specifications |
| Same mistakes repeated | Lessons learned system prevents recurrence |
| No verification step | Verifier agents actively try to break the code |
| Bugs found in production | Issues caught before release |
| Plans need interpretation | Validated plans are copy-paste ready |
DevPlan includes a public dashboard for viewing aggregate usage statistics:
Dashboard URL: devplanmcp.store/dashboard
The dashboard shows:
All analytics are privacy-preserving:
npm install
npm run dev # Local development
npm run deploy # Deploy to Cloudflare Workers
Contributions welcome! Please see the ClaudeCode-DevPlanBuilder repo for methodology details.
MIT
Be the first to review this server!
by Modelcontextprotocol · File & Storage
Secure file operations with configurable access controls
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.