PlanExe

PlanExe exposes an MCP server that lets AI agents connect to PlanExe to generate comprehensive planning outputs from plain-language goals. It enables remote or local execution paths, supporting fast integration with MCP clients to create, monitor, and download planning artifacts.

How to use

You can access PlanExe's MCP server either remotely via the official MCP endpoint or locally through a downloaded proxy or a local Docker deployment. Use an MCP client to initiate the planning workflow, supply a goal, and retrieve artifacts such as executive summaries, timelines, governance structures, and risk registers. The standard workflow involves connecting to the MCP URL, creating a task, polling for status, and downloading the resulting plan files.

How to install

Prerequisites differ by deployment path. Choose one of the following methods and follow the steps exactly to ensure a successful connection to PlanExe.

Option A remote MCP (HTTP)

Prerequisites for this path require having an account at PlanExe and a PlanExe API key. Use the remote MCP URL directly in your MCP client.

{
  "mcpServers": {
    "planexe": {
      "url": "https://mcp.planexe.org/mcp",
      "headers": {
        "X-API-Key": "pex_your_api_key_here"
      }
    }
  }
}

Option B remote MCP + local downloads via proxy (mcp_local)

If you want artifacts saved directly to your disk from your MCP client, run the local proxy.

{
  "mcpServers": {
    "planexe": {
      "command": "uv",
      "args": [
        "run",
        "--with",
        "mcp",
        "/absolute/path/to/PlanExe/mcp_local/planexe_mcp_local.py"
      ],
      "env": {
        "PLANEXE_URL": "https://mcp.planexe.org/mcp",
        "PLANEXE_MCP_API_KEY": "pex_your_api_key_here",
        "PLANEXE_PATH": "/absolute/path/for/downloads"
      }
    }
  }
}

Option C run MCP server locally with Docker

Prerequisites for this path are Docker, an OpenRouter account, and a PlanExe .env file containing OPENROUTER_API_KEY.

docker compose up --build

MCP connections and default endpoints

To connect your MCP client to the local Docker-based server, use the following endpoint: http://localhost:8001/mcp. For the local docker deployment, authentication is disabled by default in the configuration.

MCP docs and workflow references

Key MCP endpoints and flows include the setup overview, tool details and flow, MCP Inspector, Cursor, Codex, and the PlanExe MCP interface. These references help you understand how to integrate, monitor, and retrieve plan artifacts from PlanExe.

Screenshots and examples

You can input a vague description and PlanExe generates a structured plan scaffold suitable for refinement. See examples of plans such as business plans for themed concepts or pilot projects.

Help and support

If you need help or want to provide feedback, join the PlanExe Discord for community assistance and updates.

Available tools

prompt_examples

Provide example prompts to initialize and guide the MCP workflow.

task_create

Create a planning task from a plain-language goal.

task_status

Poll the status of an ongoing planning task until completion.

task_download

Download the completed planning artifacts from the MCP server.

task_file_info

Retrieve information about generated plan files.