Connect-MCP

DevPlan MCP Server

io.github.mmorris35/devplan-mcp-server · v1.0.0

Transform project ideas into paint-by-numbers development plans with phases, tasks, and subtasks.

MCPremoteno credentialsFiles & storage

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 25 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 79/100

What it does: 25 tools · 0 read, 1 write (incl. delete/pay) · Developer tools, Files & storage

No tool could be tested safely. Only read-only tools that need no input are called.

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +6
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: 0
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://devplan-mcp-server.mike-c63.workers.dev/mcp

Tools

25 tools listed at last check
  • 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_interview_questions Get interview questions to ask the user about their project. Ask these ONE AT A TIME, waiting for responses.
  • devplan_create_brief Create a PROJECT_BRIEF.md after interviewing the user. This captures their requirements in a structured format.
  • devplan_parse_brief Parse an existing PROJECT_BRIEF.md file to extract structured data. Use this if a brief already exists.
  • devplan_generate_plan 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
  • devplan_generate_claude_md Generate a CLAUDE.md scaffold (or equivalent for other targets like .cursorrules). Use this as a starting point, then enhance it.
  • devplan_list_templates List available project templates (cli, web_app, api, library). Use this to show the user what project types are supported.
  • devplan_validate_plan Validate a DEVELOPMENT_PLAN.md file for required sections and structure. Use this to check if a plan is complete.
  • devplan_get_subtask Get details for a specific subtask by ID (e.g., '0.1.1'). Use during implementation to retrieve subtask requirements.
  • devplan_update_progress Mark a subtask as complete and add completion notes. Use after finishing a subtask to update DEVELOPMENT_PLAN.md.
  • devplan_generate_executor Generate an executor agent file (.claude/agents/{project}-executor.md). This creates a specialized Haiku-powered agent for executing subtasks with full project context.
  • devplan_generate_verifier 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.
  • devplan_progress_summary Get a progress summary for a development plan. Shows completion percentage, phase-by-phase progress, next actionable subtask, and recently completed work.
  • devplan_add_lesson Add a lesson learned from verifier feedback. Lessons are stored in KV and used to improve future plan generation.
  • devplan_list_lessons List all lessons learned from previous projects. Optionally filter by project type or include archived lessons.
  • devplan_delete_lesson Delete a lesson by ID or pattern. Use this to remove outdated, incorrect, or duplicate lessons.
  • devplan_archive_lesson Archive or unarchive a lesson. Archived lessons are preserved but excluded from plan generation. Use this to retire old lessons without deleting them.
  • devplan_extract_lessons_from_report Parse a verification report and extract suggested lessons. Returns pre-filled lesson data that can be reviewed and saved with devplan_add_lesson.
  • devplan_parse_issue Parse and analyze a GitHub issue to extract structured remediation requirements. Use with: `gh issue view <number> --json number,title,body,labels,comments,url`
  • devplan_issue_to_task 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.
  • devplan_usage_stats 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 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
  • devplan_export_workflow 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.
  • devplan_export_workflow_mermaid 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.
  • 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.

Badge

Connect-MCP badge for io.github.mmorris35/devplan-mcp-server

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.github.mmorris35/devplan-mcp-server.svg)](https://clawy.uk/mcp/s/io.github.mmorris35/devplan-mcp-server)