DevPlan MCP Interface

Connect Claude Code to DevPlan for structured development planning, task breakdown, and project management guidance through a remote MCP endpoint.

When to Use This MCP Server

Connect this server when you need to:

• Break down complex feature requirements into structured development plans with ordered tasks, dependencies, and effort estimates
• Generate implementation roadmaps for new projects or major features that account for architectural decisions, testing, and deployment steps
• Get expert guidance on software development planning methodology including task prioritization, risk identification, and milestone definition

Consider alternatives when:

• You already use project management tools like Jira, Linear, or Asana with their own MCP integrations for task tracking
• Your planning needs are simple enough to be handled with a markdown checklist or the built-in Claude Code task management tools

Quick Start

Configuration

Copy
name: devplan-mcp-interface
type: mcp
category: devtools

Example Connection

Copy
claude mcp:connect devplan-mcp-interface

Available Tools

create-plan:         Generate a structured development plan from feature requirements
break-down-task:     Decompose a high-level task into subtasks with dependencies and estimates
estimate-effort:     Provide effort estimates for tasks based on complexity analysis
identify-risks:      Analyze a development plan for technical risks and mitigations
generate-milestones: Create milestone definitions with deliverables and success criteria

Core Concepts

DevPlan Platform Overview

Aspect	Details
Transport	SSE-based remote MCP endpoint at https://mcp.devplanmcp.store/sse
Planning Model	Structured task graphs with dependency tracking and critical path analysis
Estimation	Complexity-based effort estimation using historical development data
Risk Analysis	Automated identification of technical, dependency, and schedule risks
Output Format	Structured plans exportable as markdown, JSON, or project management imports

DevPlan Architecture

Claude Code IDE
    |
    v
[MCP Client] --SSE--> [DevPlan MCP Server]
                              |
                              v
                     [Planning Engine]
                      /       |        \
                Task       Estimation  Risk
              Decomposition  Engine   Analyzer
                      \       |        /
                    [Plan Graph Builder]
                              |
                              v
                     [Structured Plan Output]
                     (Tasks, Deps, Milestones)

Configuration

Parameter	Type	Default	Description
planning_depth	integer	3	Maximum depth for recursive task decomposition
include_estimates	boolean	true	Include time and effort estimates with generated plans
estimation_unit	string	hours	Unit for effort estimates: hours, story-points, or days
risk_threshold	string	medium	Minimum risk severity to include: low, medium, or high
output_format	string	markdown	Output format for generated plans: markdown, json, or both

Best Practices

1. Start with High-Level Requirements - Provide clear, concise feature descriptions to create-plan. The planning engine works best with well-defined scope boundaries and explicit acceptance criteria that constrain the solution space.

2. Use Iterative Decomposition - Start with a broad plan using shallow planning_depth, then use break-down-task on specific items that need more detail. This prevents over-planning early when requirements may still evolve.

3. Review Risk Analysis Early - Run identify-risks on your initial plan before beginning implementation. Early risk identification allows you to adjust your approach, add mitigation tasks, or flag dependencies that could block progress.

4. Calibrate Estimates to Your Team - DevPlan estimates are based on general development complexity. Adjust estimates based on your team's experience with the specific technologies and domain. Use estimates as relative sizing rather than commitments.

5. Export Plans to Your Project Management Tool - Generate plans in JSON format for importing into Jira, Linear, or other tools. This bridges the gap between AI-assisted planning and your team's established workflow tools.

Common Issues

1. SSE Connection Drops During Long Planning - The SSE connection may time out during complex plan generation. Retry the connection and break large planning requests into smaller, more focused decomposition steps.

2. Estimates Feel Too Optimistic - Default estimates assume experienced developers working without interruptions. Apply a multiplier (typically 1.5-2x) to account for meetings, reviews, testing, and unexpected complexity.

3. Plan Lacks Domain-Specific Context - The planning engine works with general software development patterns. Provide domain-specific constraints, compliance requirements, or architectural decisions in your input for more relevant plans.