Mcp

PlanExe

MCP server for generating rough-draft project plans from natural-language prompts.

Verified: 2026-05-13 (mcp-registry-ingest-2026-05-13+enrich-capability-skill)

When to use PlanExe

Choose if

You're inside an agent session and need a structured first-draft project plan — ~40-page output with WBS, Gantt, stakeholder map, risk register, SWOT — from a one-paragraph description. Useful as a scaffolding step before the human (or another agent) refines numbers, timelines, and legal/regulatory specifics. The remote MCP endpoint at mcp.planexe.org handles the long-running job lifecycle (plan_create → plan_status poll → plan_file_info), so you don't manage queueing yourself.

Avoid if

You need a client-ready plan with grounded budgets, real resource constraints, or verified legal/regulatory references — the README is explicit that "budgets are assumed rather than derived, timeline estimates are not grounded in real resource constraints, risk mitigations tend toward generic advice, and legal/regulatory details are plausible-sounding but unverified." Also avoid for short tasks (plan generation takes ~15 minutes), or when you can't fund the PlanExe account that backs the API key.

Risk Flags

  • MEDIUM data_quality README discloses that budgets, timelines, risk mitigations, and legal/regulatory references are "plausible-sounding but unverified." Treat output as scaffolding, not a deliverable.
  • LOW runtime Plan generation is a long-running job (~15 min). Agent must poll `plan_status` rather than expecting a synchronous return.
  • LOW auth Remote endpoint requires a `pex_...` API key from home.planexe.org with a funded account. Self-host path needs Docker + OpenRouter API key.

Cost

Type: Usage based

Distribution

MCP Registry
io.github.PlanExeOrg/planexe
Repository
https://github.com/PlanExeOrg/PlanExe