MCP setup
This is the shortest path to a working PlanExe MCP integration.
1. Understand the flow
- Ask for prompt examples.
- Inspect
model_profileoptions and available models. - Expand the user idea into a high-quality prompt (typically ~300-800 words) and get user approval. Use this compact shape: objective, scope, constraints, timeline, stakeholders, budget/resources, and success criteria.
- Create the plan.
- Poll for status (about every 5 minutes).
- If status is
failed, optionally callplan_retry(defaults tomodel_profile=baseline). - Download artifacts via
plan_file_info(cloud) orplan_download(mcp_local helper).
2. Minimal tool usage
example_plans(optional, preview example output)example_promptsmodel_profilesplan_createplan_statusplan_retry(optional, only for failed plans)plan_file_info
Optional local helper:
- plan_download (provided by mcp_local, not mcp_cloud)
For plan_create:
- Visible arguments:
prompt(required),model_profile(optional). - Reference: PlanExe MCP interface
3. Success criteria
- You can fetch example prompts.
- You can create a plan.
- You can fetch artifact metadata/URLs with
plan_file_info(and optionally save locally viaplan_downloadwhen usingmcp_local). - Your client can parse
error.codeanderror.messageand handle{}fromplan_file_infoas "not ready yet". - If running parallel work, your client tracks multiple
plan_ids explicitly (server-side global cap is not enforced).
Next steps
- Full tool details: MCP details
- Reference schema: PlanExe MCP interface
- App setup guides: Claude, Cursor, Codex, LM Studio