Combien d'outils expose io.github.mmorris35/devplan-mcp-server ?

io.github.mmorris35/devplan-mcp-server expose 25 outil(s). Le coût de contexte pour les charger tous est d'environ 4142 tokens (coût unique au chargement, pas par appel).

accueil / serveurs / Dev & Code / io.github.mmorris35/devplan-mcp-server

io.github.mmorris35/devplan-mcp-server

serveur MCP (Model Context Protocol) · DevPlan 1.0.0

▸ Dev & Code

[ Non encore testé ]

Verdict MCP Hub
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.

streamable-httpType / transport

directAccès

~4142 tokensCoût de contexte

25Outils

Est-ce que io.github.mmorris35/devplan-mcp-server est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.mmorris35/devplan-mcp-server » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 25 outils

devplan_add_lesson≈ 274 tokens
Add a lesson learned from verifier feedback. Lessons are stored in KV and used to improve future plan generation.
Paramètres, retour & exemple (6)
Paramètres
- fix · string · requis
  How it was fixed - the solution applied
- issue · string · requis
  What went wrong - the problem observed
- pattern · string · requis
  Pattern to watch for - a short identifier like 'Missing error handling for empty input'
- severity · string · optionnel · critical | warning | info
  Severity: critical (must fix), warning (should fix), info (nice to know)
- root_cause · string · requis
  Why it happened - the underlying cause
- project_types · array · optionnel
  Project types this applies to (e.g., ['cli', 'api']). Empty means all types.
Exemple d'appel
```
{"name": "devplan_add_lesson", "arguments": {"fix": "texte", "issue": "texte", "pattern": "texte", "root_cause": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_archive_lesson≈ 148 tokens
Archive or unarchive a lesson. Archived lessons are preserved but excluded from plan generation. Use this to retire old lessons without deleting them.
Paramètres, retour & exemple (2)
Paramètres
- archive · boolean · optionnel
  true to archive, false to unarchive
- lesson_id · string · requis
  The lesson ID to archive/unarchive (e.g., 'lesson_1234567890_abc123')
Exemple d'appel
```
{"name": "devplan_archive_lesson", "arguments": {"lesson_id": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_create_brief≈ 360 tokens
Create a PROJECT_BRIEF.md after interviewing the user. This captures their requirements in a structured format.
Paramètres, retour & exemple (10)
Paramètres
- goal · string · requis
  One-sentence project description
- name · string · requis
  Project name
- features · array · requis
  Must-have MVP features
- timeline · string · optionnel
  Project timeline (e.g., '2 weeks')
- team_size · number · optionnel
  Number of developers (default: 1)
- tech_stack · object · optionnel
  Technology preferences
- constraints · array · optionnel
  Constraints/requirements
- nice_to_have · array · optionnel
  Nice-to-have features for v2
- project_type · string · requis
  Project type: cli, web_app, api, or library
- target_users · array · requis
  Target user types
Exemple d'appel
```
{"name": "devplan_create_brief", "arguments": {"goal": "texte", "name": "texte", "features": [], "project_type": "texte", "target_users": []}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_delete_lesson≈ 161 tokens
Delete a lesson by ID or pattern. Use this to remove outdated, incorrect, or duplicate lessons.
Paramètres, retour & exemple (3)
Paramètres
- confirm · boolean · optionnel
  Set to true to actually delete. Without this, only shows what would be deleted.
- pattern · string · optionnel
  Delete lessons matching this pattern (partial match)
- lesson_id · string · optionnel
  The lesson ID to delete (e.g., 'lesson_1234567890_abc123')
Exemple d'appel
```
{"name": "devplan_delete_lesson", "arguments": {"confirm": true, "pattern": "texte", "lesson_id": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_export_workflow≈ 217 tokens
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.
Paramètres, retour & exemple (4)
Paramètres
- platform · string · optionnel · sim | n8n | reactflow | generic
  Target platform format (default: reactflow)
- plan_content · string · requis
  Full content of DEVELOPMENT_PLAN.md
- include_completed · boolean · optionnel
  Include completed subtasks in output (default: true)
- include_success_criteria · boolean · optionnel
  Include success criteria in node data (default: false)
Exemple d'appel
```
{"name": "devplan_export_workflow", "arguments": {"plan_content": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_export_workflow_mermaid≈ 164 tokens
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.
Paramètres, retour & exemple (2)
Paramètres
- plan_content · string · requis
  Full content of DEVELOPMENT_PLAN.md
- include_completed · boolean · optionnel
  Include completed subtasks in output (default: true)
Exemple d'appel
```
{"name": "devplan_export_workflow_mermaid", "arguments": {"plan_content": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_extract_lessons_from_report≈ 151 tokens
Parse a verification report and extract suggested lessons. Returns pre-filled lesson data that can be reviewed and saved with devplan_add_lesson.
Paramètres, retour & exemple (2)
Paramètres
- project_type · string · optionnel
  Project type to associate with extracted lessons (e.g., 'cli', 'api')
- report_content · string · requis
  The full verification report markdown content
Exemple d'appel
```
{"name": "devplan_extract_lessons_from_report", "arguments": {"report_content": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_generate_claude_md≈ 207 tokens
Generate a CLAUDE.md scaffold (or equivalent for other targets like .cursorrules). Use this as a starting point, then enhance it.
Paramètres, retour & exemple (4)
Paramètres
- target · string · optionnel · claude | cursor | aider | cline | windsurf | generic
  Target tool (claude, cursor, aider, cline, windsurf, generic)
- language · string · optionnel
  Primary language
- brief_content · string · requis
  PROJECT_BRIEF.md or JSON brief
- test_coverage · number · optionnel
  Required coverage percentage
Exemple d'appel
```
{"name": "devplan_generate_claude_md", "arguments": {"brief_content": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_generate_executor≈ 192 tokens
Generate an executor agent file (.claude/agents/{project}-executor.md). This creates a specialized Haiku-powered agent for executing subtasks with full project context.
Paramètres, retour & exemple (3)
Paramètres
- target · string · optionnel · claude | cursor | aider | cline | windsurf | generic
  Target tool (default: claude)
- language · string · optionnel
  Primary language (python or typescript)
- brief_content · string · requis
  PROJECT_BRIEF.md content or JSON brief
Exemple d'appel
```
{"name": "devplan_generate_executor", "arguments": {"brief_content": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_generate_plan≈ 407 tokens
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.
Paramètres, retour & exemple (4)
Paramètres
- target · string · optionnel · claude | cursor | aider | cline | windsurf | generic
  Target AI tool/model for agent file generation (default: claude)
- template · string · optionnel
  Template override
- min_severity · string · optionnel · critical | warning | info
  Minimum severity of lessons to include. 'critical' = only critical, 'warning' = critical + warning, 'info' = all (default)
- brief_content · string · requis
  PROJECT_BRIEF.md or JSON brief
Exemple d'appel
```
{"name": "devplan_generate_plan", "arguments": {"brief_content": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_generate_verifier≈ 195 tokens
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.
Paramètres, retour & exemple (3)
Paramètres
- target · string · optionnel · claude | cursor | aider | cline | windsurf | generic
  Target tool (default: claude)
- language · string · optionnel
  Primary language (python or typescript)
- brief_content · string · requis
  PROJECT_BRIEF.md content or JSON brief
Exemple d'appel
```
{"name": "devplan_generate_verifier", "arguments": {"brief_content": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_get_subtask≈ 125 tokens
Get details for a specific subtask by ID (e.g., '0.1.1'). Use during implementation to retrieve subtask requirements.
Paramètres, retour & exemple (2)
Paramètres
- subtask_id · string · requis
  ID in format X.Y.Z
- plan_content · string · requis
  DEVELOPMENT_PLAN.md content
Exemple d'appel
```
{"name": "devplan_get_subtask", "arguments": {"subtask_id": "texte", "plan_content": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_implement≈ 85 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel
```
{"name": "devplan_implement", "arguments": {}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_interview_questions≈ 68 tokens
Get interview questions to ask the user about their project. Ask these ONE AT A TIME, waiting for responses.
Paramètres, retour & exemple (0)
Exemple d'appel
```
{"name": "devplan_interview_questions", "arguments": {}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_issue_to_task≈ 283 tokens
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.
Paramètres, retour & exemple (5)
Paramètres
- mode · string · optionnel · append | standalone
  'append' generates content to add to existing plan, 'standalone' creates full REMEDIATION_PLAN.md
- language · string · optionnel
  Primary language (python, typescript) for appropriate test patterns
- project_type · string · optionnel
  Project type for context (cli, web_app, api, library)
- existing_plan · string · optionnel
  Existing DEVELOPMENT_PLAN.md content. If provided, generates task IDs that don't conflict with existing R.X phases.
- issue_content · string · requis
  JSON output from `gh issue view <number> --json number,title,body,labels,comments,url`
Exemple d'appel
```
{"name": "devplan_issue_to_task", "arguments": {"issue_content": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_list_lessons≈ 135 tokens
List all lessons learned from previous projects. Optionally filter by project type or include archived lessons.
Paramètres, retour & exemple (2)
Paramètres
- project_type · string · optionnel
  Filter lessons for a specific project type (e.g., 'cli', 'api', 'web_app')
- include_archived · boolean · optionnel
  Include archived lessons in the list
Exemple d'appel
```
{"name": "devplan_list_lessons", "arguments": {"project_type": "texte", "include_archived": true}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_list_templates≈ 125 tokens
List available project templates (cli, web_app, api, library). Use this to show the user what project types are supported.
Paramètres, retour & exemple (2)
Paramètres
- project_type · string · optionnel
  Filter by type
- response_format · string · optionnel · json | markdown
  Output format
Exemple d'appel
```
{"name": "devplan_list_templates", "arguments": {"project_type": "texte", "response_format": "json"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_parse_brief≈ 128 tokens
Parse an existing PROJECT_BRIEF.md file to extract structured data. Use this if a brief already exists.
Paramètres, retour & exemple (2)
Paramètres
- content · string · requis
  Full PROJECT_BRIEF.md content
- response_format · string · optionnel · json | markdown
  Output format
Exemple d'appel
```
{"name": "devplan_parse_brief", "arguments": {"content": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_parse_issue≈ 130 tokens
Parse and analyze a GitHub issue to extract structured remediation requirements. Use with: `gh issue view <number> --json number,title,body,labels,comments,url`
Paramètres, retour & exemple (1)
Paramètres
- issue_content · string · requis
  JSON output from `gh issue view <number> --json number,title,body,labels,comments,url`
Exemple d'appel
```
{"name": "devplan_parse_issue", "arguments": {"issue_content": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_progress_summary≈ 114 tokens
Get a progress summary for a development plan. Shows completion percentage, phase-by-phase progress, next actionable subtask, and recently completed work.
Paramètres, retour & exemple (1)
Paramètres
- plan_content · string · requis
  DEVELOPMENT_PLAN.md content
Exemple d'appel
```
{"name": "devplan_progress_summary", "arguments": {"plan_content": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_start≈ 86 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel
```
{"name": "devplan_start", "arguments": {}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_update_progress≈ 149 tokens
Mark a subtask as complete and add completion notes. Use after finishing a subtask to update DEVELOPMENT_PLAN.md.
Paramètres, retour & exemple (3)
Paramètres
- subtask_id · string · requis
  ID to mark complete
- plan_content · string · requis
  Current plan content
- completion_notes · string · requis
  Notes about completion
Exemple d'appel
```
{"name": "devplan_update_progress", "arguments": {"subtask_id": "texte", "plan_content": "texte", "completion_notes": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_usage_stats≈ 134 tokens
View usage statistics showing how requests are distributed across users. Helps understand if usage is concentrated among few users or spread across many.
Paramètres, retour & exemple (2)
Paramètres
- date · string · optionnel
  Date to query (YYYY-MM-DD format). Defaults to today.
- days · number · optionnel
  Number of days to include (1-30). Defaults to 7.
Exemple d'appel
```
{"name": "devplan_usage_stats", "arguments": {"date": "texte", "days": 1}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_validate_haiku_executable≈ 164 tokens
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.
Paramètres, retour & exemple (1)
Paramètres
- plan_content · string · requis
  Full content of DEVELOPMENT_PLAN.md to validate
Exemple d'appel
```
{"name": "devplan_validate_haiku_executable", "arguments": {"plan_content": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
devplan_validate_plan≈ 124 tokens
Validate a DEVELOPMENT_PLAN.md file for required sections and structure. Use this to check if a plan is complete.
Paramètres, retour & exemple (2)
Paramètres
- strict · boolean · optionnel
  Treat warnings as errors
- content · string · requis
  DEVELOPMENT_PLAN.md content
Exemple d'appel
```
{"name": "devplan_validate_plan", "arguments": {"content": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

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