PlanExe

planexeorg/planexe

Planexe exposes an MCP server that enables AI agents to generate comprehensive strategic plans from plain-English goal statements in approximately 15 minutes. The server provides planning capabilities that produce structured outputs including executive summaries, Gantt charts, governance structures, role descriptions, stakeholder maps, risk registers, and SWOT analyses, solving the problem of rapidly transforming high-level ideas into detailed, domain-aware first-draft plans. While the generated plans serve as strong scaffolding for brainstorming and outlining, users should treat outputs as starting points requiring refinement, particularly for budgets, timeline estimates, risk mitigations, and regulatory details.

GitHub stars: 381
tools: 11
auth: Secret needed
transport: HTTP
last updated: Feb 21, 2026

View on GitHub

Tools

11 tools

Public tool metadata for what this MCP can expose to an agent.

example_plansReturns a curated list of example plans with download links for reports and zip bundles. Use this to preview what PlanExe output looks like before creating your own plan. Especially useful when the user asks what the output looks like before committing to a plan. No API key re...

Returns a curated list of example plans with download links for reports and zip bundles. Use this to preview what PlanExe output looks like before creating your own plan. Especially useful when the user asks what the output looks like before committing to a plan. No API key re...

No parameter schema in public metadata yet.

example_promptsCall this first. Returns example prompts that define what a good prompt looks like. Do NOT call plan_create yet. Optional before plan_create: call model_profiles to choose model_profile. Next is a non-tool step: formulate a detailed prompt (typically ~300-800 words; use exampl...

Call this first. Returns example prompts that define what a good prompt looks like. Do NOT call plan_create yet. Optional before plan_create: call model_profiles to choose model_profile. Next is a non-tool step: formulate a detailed prompt (typically ~300-800 words; use exampl...

No parameter schema in public metadata yet.

model_profilesOptional helper before plan_create. Returns model_profile options with plain-language guidance and currently available models in each profile. If no models are available, returns error code MODEL_PROFILES_UNAVAILABLE.

Optional helper before plan_create. Returns model_profile options with plain-language guidance and currently available models in each profile. If no models are available, returns error code MODEL_PROFILES_UNAVAILABLE.

No parameter schema in public metadata yet.

plan_createCall only after example_prompts and after you have completed prompt drafting/approval (non-tool step). PlanExe turns the approved prompt into a strategic project-plan draft (20+ sections) in ~10-20 min. Sections include: executive summary, interactive Gantt charts, investor pi...3 params

Call only after example_prompts and after you have completed prompt drafting/approval (non-tool step). PlanExe turns the approved prompt into a strategic project-plan draft (20+ sections) in ~10-20 min. Sections include: executive summary, interactive Gantt charts, investor pi...

Parameters* required

model_profilestring

Model profile: baseline, premium, frontier, custom. Call model_profiles to inspect options.one of baseline · premium · frontier · customdefault: baseline

promptstring

start_datevalue

Optional plan start date in ISO 8601 format with timezone offset (e.g. '2025-06-15T09:00:00+02:00'). When omitted, the plan starts now. Use this to set a past or future start date for the plan.

plan_statusReturns status and progress of the plan currently being created. This is the primary way to check progress — it returns structured JSON with all progress fields. Poll at reasonable intervals (e.g. every 5 minutes): plan generation typically takes 10-20 minutes (baseline profil...1 params

Returns status and progress of the plan currently being created. This is the primary way to check progress — it returns structured JSON with all progress fields. Poll at reasonable intervals (e.g. every 5 minutes): plan generation typically takes 10-20 minutes (baseline profil...

Parameters* required

plan_idstring

Plan UUID returned by plan_create.

plan_stopRequest the plan generation to stop. Pass the plan_id (the UUID returned by plan_create). Stopping is asynchronous: the stop flag is set immediately but the plan may continue briefly before halting. A stopped plan will transition to the stopped state. If the plan is already co...1 params

Request the plan generation to stop. Pass the plan_id (the UUID returned by plan_create). Stopping is asynchronous: the stop flag is set immediately but the plan may continue briefly before halting. A stopped plan will transition to the stopped state. If the plan is already co...

Parameters* required

plan_idstring

Plan UUID returned by plan_create. Use it to stop the plan creation.

plan_retryRetry a plan that is currently in failed or stopped state. Pass the plan_id and optionally model_profile (defaults to baseline). The plan is reset to pending, prior artifacts are cleared, and the same plan_id is requeued for processing. Returns PLAN_NOT_FOUND when plan_id is u...2 params

Retry a plan that is currently in failed or stopped state. Pass the plan_id and optionally model_profile (defaults to baseline). The plan is reset to pending, prior artifacts are cleared, and the same plan_id is requeued for processing. Returns PLAN_NOT_FOUND when plan_id is u...

Parameters* required

model_profilestring

Model profile used for retry. Defaults to baseline.one of baseline · premium · frontier · customdefault: baseline

plan_idstring

UUID of the failed plan to retry.

plan_resumeResume a failed or stopped plan without discarding completed intermediary files. Plan generation restarts from the first incomplete step, skipping all steps that already produced output files. Use plan_resume when plan_status shows 'failed' or 'stopped' and plan generation was...2 params

Resume a failed or stopped plan without discarding completed intermediary files. Plan generation restarts from the first incomplete step, skipping all steps that already produced output files. Use plan_resume when plan_status shows 'failed' or 'stopped' and plan generation was...

Parameters* required

model_profilestring

Model profile used for the resumed plan. Defaults to baseline.one of baseline · premium · frontier · customdefault: baseline

plan_idstring

UUID of the failed plan to resume.

plan_file_infoReturns file metadata (content_type, download_url, download_size, expires_at) for the report or zip artifact. Use artifact='report' (default) for the interactive HTML report (~700KB, self-contained with embedded JS for collapsible sections and interactive Gantt charts — open i...2 params

Returns file metadata (content_type, download_url, download_size, expires_at) for the report or zip artifact. Use artifact='report' (default) for the interactive HTML report (~700KB, self-contained with embedded JS for collapsible sections and interactive Gantt charts — open i...

Parameters* required

artifactstring

Download artifact type: report or zip.one of report · zipdefault: report

plan_idstring

Plan UUID returned by plan_create. Use it to download the created plan.

plan_listList the most recent plans for an authenticated user. Returns up to `limit` plans (default 10, max 50) newest-first, each with plan_id, state, progress_percentage, created_at (ISO 8601), and a prompt_excerpt (first 100 chars). Use this to recover a lost plan_id or to review re...1 params

List the most recent plans for an authenticated user. Returns up to `limit` plans (default 10, max 50) newest-first, each with plan_id, state, progress_percentage, created_at (ISO 8601), and a prompt_excerpt (first 100 chars). Use this to recover a lost plan_id or to review re...

Parameters* required

limitinteger

Maximum number of plans to return (1–50). Newest plans are returned first.default: 10

send_feedbackSubmit feedback about PlanExe — issues, impressions, or suggestions. Callable at any point in the workflow; fire-and-forget, never blocks. Use category to classify: mcp (MCP tools, SSE, plan_status, workflow), plan (the generated output files), code (PlanExe source), docs (doc...4 params

Submit feedback about PlanExe — issues, impressions, or suggestions. Callable at any point in the workflow; fire-and-forget, never blocks. Use category to classify: mcp (MCP tools, SSE, plan_status, workflow), plan (the generated output files), code (PlanExe source), docs (doc...

Parameters* required

categorystring

Feedback category: mcp, plan, code, docs, or other.

messagestring

Free-text feedback. Include environment context if reporting an issue.

plan_idvalue

Optional plan UUID to attach this feedback to.

ratingvalue

Sentiment: 1=strong negative, 2=weak negative, 3=neutral, 4=weak positive, 5=strong positive.