PlanExe
Turn a plain-language product idea into a rough-draft project plan inside the agent before you commit engineering time or write a full spec.
Overview
PlanExe is an MCP server for the Validate phase that generates rough-draft project plans from natural-language prompts through PlanExe’s authenticated remote MCP endpoint.
What is this MCP server?
- Remote MCP at mcp.planexe.org/mcp generates rough-draft project plans from natural-language prompts
- Authenticated with X-API-Key using a PlanExe UserApiKey (typically pex_ prefix) from home.planexe.org
- Streamable-http transport for Claude Code, Cursor, and other remote-capable MCP clients
- Outputs planning artifacts meant as starting drafts, not finalized enterprise PM exports
- Official site and docs at mcp.planexe.org tied to the PlanExe GitHub repository
- Published MCP server version 1.0.0 in the registry schema
- Remote endpoint https://mcp.planexe.org/mcp with required X-API-Key header
- Stated capability: rough-draft project plans from natural-language prompts only
Community signal: 381 GitHub stars.
What problem does it solve?
Founders stall at the fuzzy middle between an idea in chat and a plan their agent or team can execute because manually structuring scope takes too long.
Who is it for?
Solo builders validating a new SaaS or agent product who want a quick structured plan draft without leaving Claude Code or Cursor.
Skip if: Teams that need audited enterprise PM integrations, legally binding statements of work, or automated code generation from the same server.
What do I get? / Deliverables
After you add the PlanExe remote MCP with your pex_ API key, you can ask the agent to produce a first-pass project plan you can refine into milestones, tickets, or a formal spec.
- Rough-draft project plan text generated from your natural-language description
- Structured planning sections suitable for editing into a PRD or ticket backlog
- Repeatable agent workflow for re-scoping when requirements change
Recommended MCP Servers
Journey fit
PlanExe generates project plans from prompts at the moment you are defining what to build; that maps to Validate when scope, milestones, and risks still need a fast first pass. Scope is where builders narrow features, phases, and deliverables; a plan-generation MCP belongs on the scope shelf rather than on implementation integrations.
How it compares
Remote plan-drafting MCP API, not a local brainstorming skill or a Gantt export from your issue tracker.
Common Questions / FAQ
Who is PlanExe MCP for?
It is for indie developers and solo founders who use MCP-enabled agents and want natural-language prompts converted into rough project plans before full build-out.
When should I use PlanExe MCP?
Use it in Validate when you are scoping a feature set, MVP, or side project and need a structured draft plan to critique, trim, or convert into tasks.
How do I add PlanExe MCP to my agent?
Obtain a UserApiKey from home.planexe.org (usually prefixed pex_), then configure the streamable-http remote https://mcp.planexe.org/mcp with header X-API-Key in your MCP client’s server settings.