mcp server
DevPlan MCP Server
Transform project ideas into paint-by-numbers development plans with phases, tasks, and subtasks.
Description as published by the maintainer. Source
- version 1.0.0
- slowing
slowing — Registry entry last updated 2025-12-11.
What this server can do
25 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
devplan_add_lesson(fix, issue, pattern, severity, root_cause, project_types)- Add a lesson learned from verifier feedback. Lessons are stored in KV and used to improve future plan generation. Required: issue, root_cause, fix, pattern.
devplan_archive_lesson(archive, lesson_id)- Archive or unarchive a lesson. Archived lessons are preserved but excluded from plan generation. Use this to retire old lessons without deleting them. Required: lesson_id.
devplan_create_brief(goal, name, features, timeline, team_size, tech_stack, constraints, nice_to_have, project_type, target_users)- Create a PROJECT_BRIEF.md after interviewing the user. This captures their requirements in a structured format. Required: name, project_type, goal, target_users, features.
devplan_delete_lesson(confirm, pattern, lesson_id)- Delete a lesson by ID or pattern. Use this to remove outdated, incorrect, or duplicate lessons.
devplan_export_workflow(platform, plan_content, include_completed, include_success_criteria)- Export a DEVELOPMENT_PLAN.md as ReactFlow-compatible JSON for visual workflow tools like Sim.ai. Returns nodes, edges, and metadata for rendering the plan as an interactive diagram. Required: plan_content.
devplan_export_workflow_mermaid(plan_content, include_completed)- Export a DEVELOPMENT_PLAN.md as a Mermaid flowchart diagram in markdown format. Perfect for embedding in documentation or viewing in VS Code/GitHub. Save the output as workflow.md to get a visual representation of your plan. Required: plan_content.
devplan_extract_lessons_from_report(project_type, report_content)- Parse a verification report and extract suggested lessons. Returns pre-filled lesson data that can be reviewed and saved with devplan_add_lesson. Required: report_content.
devplan_generate_claude_md(target, language, brief_content, test_coverage)- Generate a CLAUDE.md scaffold (or equivalent for other targets like .cursorrules). Use this as a starting point, then enhance it. Required: brief_content.
devplan_generate_executor(target, language, brief_content)- Generate an executor agent file (.claude/agents/{project}-executor.md). This creates a specialized Haiku-powered agent for executing subtasks with full project context. Required: brief_content.
devplan_generate_plan(target, template, min_severity, brief_content)- Generate a DEVELOPMENT_PLAN.md scaffold. IMPORTANT: This outputs a SCAFFOLD, not a finished plan. REQUIRED WORKFLOW (you MUST follow this): 1. Call this tool to get the scaffold, optionally specifying target (claude, cursor, aider, cline, windsurf, generic) 2. ENHANCE the scaffold by: - Reading the project's existing codebase - Writing COMPLETE file contents for each subtask (no "Add to" instructions) - Including ALL imports in every code block - Making test fixtures self-contained in each test file - Providing exact line context for any file modifications 3. Call devplan_validate_haiku_executable to verify the plan 4. If validation fails, fix the issues and re-validate 5. ONLY present the plan to the user after validation passes The user should NEVER see the raw scaffold - only the enhanced, validated plan. Required: brief_content.
devplan_generate_verifier(target, language, brief_content)- Generate a verifier agent file (.claude/agents/{project}-verifier.md). This creates a Sonnet-powered agent for validating completed applications against PROJECT_BRIEF.md requirements. Required: brief_content.
devplan_get_subtask(subtask_id, plan_content)- Get details for a specific subtask by ID (e.g., '0.1.1'). Use during implementation to retrieve subtask requirements. Required: plan_content, subtask_id.
devplan_implement- One-command kickoff to implement an entire development plan. Returns instructions for Claude Code to use the executor agent to build the project, then the verifier agent to validate it.
devplan_interview_questions- Get interview questions to ask the user about their project. Ask these ONE AT A TIME, waiting for responses.
devplan_issue_to_task(mode, language, project_type, existing_plan, issue_content)- Convert a GitHub issue into a remediation task with subtasks. Returns markdown suitable for appending to DEVELOPMENT_PLAN.md or creating a standalone REMEDIATION_PLAN.md. Required: issue_content.
devplan_list_lessons(project_type, include_archived)- List all lessons learned from previous projects. Optionally filter by project type or include archived lessons.
devplan_list_templates(project_type, response_format)- List available project templates (cli, web_app, api, library). Use this to show the user what project types are supported.
devplan_parse_brief(content, response_format)- Parse an existing PROJECT_BRIEF.md file to extract structured data. Use this if a brief already exists. Required: content.
devplan_parse_issue(issue_content)- Parse and analyze a GitHub issue to extract structured remediation requirements. Use with: `gh issue view <number> --json number,title,body,labels,comments,url` Required: issue_content.
devplan_progress_summary(plan_content)- Get a progress summary for a development plan. Shows completion percentage, phase-by-phase progress, next actionable subtask, and recently completed work. Required: plan_content.
devplan_start- START HERE: Initialize a new project using the DevPlan methodology. This tool provides comprehensive inline instructions for building a development plan that Claude Code can execute step-by-step.
devplan_update_progress(subtask_id, plan_content, completion_notes)- Mark a subtask as complete and add completion notes. Use after finishing a subtask to update DEVELOPMENT_PLAN.md. Required: plan_content, subtask_id, completion_notes.
devplan_usage_stats(date, days)- View usage statistics showing how requests are distributed across users. Helps understand if usage is concentrated among few users or spread across many.
devplan_validate_haiku_executable(plan_content)- Validate that a DEVELOPMENT_PLAN.md is Haiku-executable (can be implemented by Claude Haiku without interpretation). Returns specific errors with fix instructions. IMPORTANT: After calling devplan_generate_plan, you MUST enhance the scaffold with complete code, then call this tool to validate before presenting to the user. Required: plan_content.
devplan_validate_plan(strict, content)- Validate a DEVELOPMENT_PLAN.md file for required sections and structure. Use this to check if a plan is complete. Required: content.
Last successful function declaration observed on . Source: https://devplan-mcp-server.mike-c63.workers.dev/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://devplan-mcp-server.mike-c63.workers.dev/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2025-12-11 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2025-12-11 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 25 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | devplan-mcp-server.mike-c63.workers.dev | |
| mcp endpoint status | ok | The server listed 25 functions when asked. | as of probe | devplan-mcp-server.mike-c63.workers.dev |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json