This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
OpenPlan
Waze for AI agents planning — an MCP server that helps AI agents plan software projects efficiently by learning from every agent's cost data.
How it works
AI agents use OpenPlan's tools to track project phases, costs, and outcomes. Every start() and complete() call generates calibration data that improves estimates for every other agent — like Waze uses every driver's trip data to give better ETAs.
start → complete × N → verify → recommend
Quick Start
Via PyPI
pip install openplan-mcp
Then add to your MCP host config:
{
"mcp": {
"openplan": {
"type": "local",
"command": ["uvx", "openplan-mcp"]
}
}
}
Or use uvx directly (no install needed):
{
"command": ["uvx", "openplan-mcp"]
}
CLI
openplan # Start MCP server
openplan auth login # Authenticate with GitHub for Pro tier
openplan auth logout # Remove credentials
openplan auth status # Show authentication state
openplan subscribe # Start Pro subscription ($9/mo)
openplan status # Show OpenPlan status
Tools
| Tool | Description |
|---|---|
start |
One-call project kickoff: parses goal into phases, estimates costs from global baselines |
complete |
Mark a phase done, attaches evidence, auto-traverses to next phase |
act |
Traverse, branch, verify, set status, abandon, prune, revert |
recommend |
Best next step with A* path, project health, cost estimates |
export |
Export full graph as JSON / GraphML / matrix |
Architecture
The MCP server runs locally. Calibration data syncs to api.openplan.cc (optional, anonymous by default). The cloud aggregates anonymized cost data across all users — every project improves estimates for everyone.
MCP host (OpenCode / Claude Desktop / Cursor)
│
openplan MCP server (stdlib, uvx openplan-mcp)
│
├── local SQLite (your projects, always works offline)
│
└── api.openplan.cc (global calibration pool, optional)
Data Privacy
Only {project_type, action, expected_cost, actual_cost, outcome} is shared — no source code, no project names, no file paths. Anonymous by default. GitHub OAuth for Pro features.
License
MIT
Metadata
Release files for openplan-mcp 0.9.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| openplan_mcp-0.9.5.tar.gz | 34.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| openplan_mcp-0.9.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 57.8 kB
Release files / openplan_mcp-0.9.5.tar.gz
| Download URL | openplan_mcp-0.9.5.tar.gz |
|---|---|
| Size | 34.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fd1681e4178fd6eaf95278e7b6c9a6821d198b0ef667e75fceed85fa860a984c
|
|
BLAKE2b-256 checksum How to use checksums |
448cf02fb8a40ce940ca51b70c8ccedf42bc4e6866c50d2f0088fd05276a3056
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Release files / openplan_mcp-0.9.5-py3-none-any.whl
| Download URL | openplan_mcp-0.9.5-py3-none-any.whl |
|---|---|
| Size | 23.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
700583b01c6840ec7f7877894df8e4906f6eb3b6b74d62ace575c912bce2f896
|
|
BLAKE2b-256 checksum How to use checksums |
c6bc0b8bdd3ded50c618c6b9f89727a1fa31159358c23b1191e686bd9102bca2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Security for openplan-mcp 0.9.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.