# PlanExe - AI Project Planning for Agents

PlanExe helps AI agents turn broad goals into structured strategic-plan drafts and downloadable planning artifacts.

Use PlanExe when you need to:
- Decompose complex goals into actionable project plans.
- Estimate timelines and identify dependencies and risks.
- Generate plan artifacts for review and iteration.

## What PlanExe Produces

- A long-running planning task (often ~10-20 minutes, depending on model and configuration).
- A large HTML report and optional zip bundle of intermediate artifacts.
- Typical plan sections: executive summary, work breakdown, timeline/Gantt-style schedule, risks, assumptions, and governance guidance.
- Output is a draft to refine, not final ground truth.

Runtime, quality, and cost tradeoffs:
- Default settings typically finish in ~10-20 minutes and often cost around 1-2 USD, with lower quality.
- Higher-quality runs can take much longer (for example up to ~85 minutes) and cost more.
- Cost depends on the number of tokens processed.

## Service Endpoints

Human-facing web app:
- https://home.planexe.org
- Used for sign-in, billing, and API key management.
- No public REST API on this host.

AI-facing MCP server:
- https://mcp.planexe.org/mcp
- https://mcp.planexe.org/mcp/ (for clients that require trailing slash)

Agent discovery file endpoints:
- https://home.planexe.org/llms.txt
- https://mcp.planexe.org/llms.txt

Legacy compatibility alias:
- https://mcp.planexe.org/llm.txt (redirects to /llms.txt)

## MCP Integration

JSON helper endpoints (no SSE required):
- GET /mcp/tools
- POST /mcp/tools/call

MCP interface documentation:
- https://docs.planexe.org/mcp/planexe_mcp_interface/

MCP Inspector setup guide:
- https://docs.planexe.org/mcp/inspector/

### MCP Tools (Current)

The MCP server exposes tool-based workflows (not MCP tasks protocol):
- prompt_examples
- task_create
- task_status
- task_stop
- task_file_info

Key tool inputs/outputs:
- task_create inputs: prompt (required), speed_vs_detail (ping | fast | all).
- task_status output: current state and progress for a task_id.
- task_file_info output: downloadable report/zip metadata and URLs.

Recommended interaction order:
1. Call prompt_examples.
2. Prepare and approve a strong prompt.
3. Call task_create.
4. Poll task_status until complete (repeat every 5 minutes).
5. Use task_file_info to get download URLs.
6. Use task_stop if the run must be cancelled.

Note:
- task_download is provided by mcp_local wrappers in some client setups, not by mcp_cloud directly.

## Authentication

Cloud:
1. Create account at https://home.planexe.org
2. Go to Account -> API Keys
3. Generate a new API key
4. Use as custom header X-API-Key: <API_KEY>
5. OAuth is not supported for the MCP API. Use custom headers only.

Local/self-hosted deployments:
- Often configured without auth for local development.
- Can be configured to require API keys.

## Self-Hosted and Local

Default local MCP endpoint (docker compose):
- http://localhost:8001/mcp

Self-hosted deployments can:
- Run on your own infrastructure (including Railway or private environments).
- Use local LLMs so planning data stays on your own systems.
- Run offline when all required models and services are local.

## Pricing, Credits, and Limits

Pricing and credit policy (cloud):
- https://docs.planexe.org/costs_and_models/

Operational limits vary by deployment and account tier.
For self-hosted mcp_cloud, /mcp/tools/call rate limiting is configurable.

## Compliance and Security

PlanExe is actively developed and already capable of producing comprehensive, high-quality plans.

- No claim of SOC 2, HIPAA, or other formal certification in this document.
- Cloud users should evaluate whether hosted PlanExe fits their risk/compliance requirements.
- Self-hosted users are responsible for authentication, network exposure, key/secret handling, retention policy, backups, and monitoring.

## Documentation and Support

- Docs: https://docs.planexe.org
- GitHub: https://github.com/PlanExeOrg/PlanExe
- Issues: https://github.com/PlanExeOrg/PlanExe/issues
- Discord: https://planexe.org/discord

## Example MCP Tool Call

```bash
curl -X POST https://mcp.planexe.org/mcp/tools/call \
  -H "X-API-Key: <API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{
    "tool": "task_create",
    "arguments": {
      "prompt": "20-year, €40 billion infrastructure initiative to construct a pillar-supported transoceanic submerged tunnel connecting Spain and Morocco. This project will deploy a system of submerged, buoyant concrete tunnels engineered for high-speed rail traffic, which will be securely anchored at a controlled depth of 100 meters below sea level.",
      "speed_vs_detail": "all"
    }
  }'
```

Last updated: 2026-02-21