Public Beta — codeplans.ai
Engineering changes
don't fit in
a ticket column.
CodePlans is the planning layer between your issue tracker and your architecture — mapping demand (features, bugs, tech debt) onto coordinated change across services, libraries, and datastores. Native tasks or mirrored from the tools you already use.
Agent-native: full MCP server for Claude Code & Cursor
v0.3.x · 25 releases · MIT licensed · Free to self-host
The coordination gap
A refactor that touches twelve services has no home in your current tooling.
01
Context dissolves across tools
Decisions live in Slack. Tasks live in Jira. Architecture lives in Confluence. The picture never fully assembles.
02
Tickets don't understand architecture
No issue tracker knows what a service is, or that your checkout flow depends on three of them. CodePlans does.
03
Managers fly blind until it's late
Progress becomes visible only at stand-ups. By the time a plan is behind, it's already a problem.
04
Your AI agents have no map
Claude Code and Cursor can write the code, but they can't see what's planned, what's owned, or what's debt. CodePlans gives agents a queryable, writable model of your engineering intent.
The conceptual model
Your system,
finally structured
for change.
CodePlans separates demand from delivery. Work items capture what's needed; code plans coordinate how it ships across your assets; tasks track the work. Every item knows which plans address it, every plan knows which assets it touches — traceability from complaint to commit.
Open tech-debt items automatically roll up into a severity-weighted debt score per asset — a live debt register, not a stale spreadsheet.
LAYER 01
Products
A bounded system — everything belonging to a platform, team, or service domain. The top-level planning unit that groups all your assets.
LAYER 02
Assets
The individual components: apps, services, libraries, datastores, platforms. Tagged, health-scored, and linked through dependency relationships.
LAYER 03
Work Items
The demand side: features, bugs, UX issues, and tech debt. Created natively, filed by AI agents, or mirrored automatically from GitHub, GitLab, Jira, Asana, or Linear. Linked many-to-many to the plans that address them.
LAYER 04
Code Plans
Named, scoped, typed. A code plan targets specific assets, carries a schedule, and decomposes into tasks tracked to completion. Every plan links back to the work items it resolves.
Built for the agent workflow
Point Claude at your repo.
Get a living plan.
The /codeplans-capture skill reads your docs folder and builds the model — plans from design docs, work items from draft specs and remediation backlogs, debt from code notes. Re-run it as the repo evolves; records reconcile by spec URL instead of duplicating.
Agents keep it current.
/codeplans-logrecords each coding session's work — tasks done, PRs opened, effort spent — so the plan reflects reality without anyone updating a board.
# Claude Code
$ claude mcp add --scope user --transport http codeplans \
https://your-host/api/mcp/mcp \
--header "Authorization: Bearer cpk_…"
# Cursor — add to ~/.cursor/mcp.json
{
"mcpServers": {
"codeplans": {
"url": "https://your-host/api/mcp/mcp",
"headers": { "Authorization": "Bearer cpk_…" }
}
}
}Integrations
Connects to the tools you already use.
Mirror work items from five trackers with strict provenance, and give your AI agents a queryable model of your engineering intent over MCP. All of it works in the OSS self-hosted build.
Issue trackers · pull-only sync
AI agents · via MCP
Deployment options
Run it where you work.
Keep what matters to you.
Self-hosted
Full control. One server. Run CodePlans on your own infrastructure with a single-file SQLite database — or point it at PostgreSQL when you want a shared, production-grade backend. No cloud dependency, no cost. MIT licensed.
- ✓SQLite backend — single-file, zero config (PostgreSQL optional)
- ✓Deploy on any VPS, container, or home server
- ✓Local auth (bcrypt + sessions), closed/invite/open registration modes, email invitations
- ✓All five tracker integrations + full MCP server — nothing is hosted-only
- ✓Integration tokens encrypted at rest (AES-256-GCM)
- ✓MIT licensed — fork it, extend it, ship it
CodePlans.ai
Production-ready, without the ops overhead. Supabase-backed PostgreSQL, managed hosting, and multi-org features landing soon. In public beta now.
- ✓Supabase Auth + PostgreSQL — production grade
- ✓Team accounts with role-based access
- ✓Multi-org workspaces, SSO & team billing (in development)
- ✓AI effort estimation and plan insights (roadmap)
- ✓Public beta — free early access now
What's coming
Shipping in the open,
with a clear north star.
Live today
Full MCP server
28 tools over Streamable HTTP. Claude Code and Cursor read plans, file work items, model products and dependencies, log session work, and capture your repo's /docs into structured plans.
Live today
Five tracker integrations
GitHub, GitLab, Jira, Asana, and Linear. Pull-only mirroring with strict provenance — tracker-owned fields stay read-only, your annotations stay yours. PR auto-linking updates delivery status.
Live today
Dependency mapping
Map relationships across your assets with plan impact analysis — see what a change ripples into before you commit.
Live today
Tech debt scoring
Severity-weighted rollup from open debt items into a live debt score per asset. Deterministic, works today — no AI required.
Live today
Spec-linked work
Link markdown specs in your repo to plans and work items; CodePlans renders them in-app using your connection's credentials.
Coming soon
AI assistance
Effort estimation and plan insights, scheduled sync with webhooks, and hosted multi-org billing — the honest remainder still in flight.
Early access · Public beta
Your next big refactor
deserves a proper plan.
CodePlans is in public beta. Join early and help shape how engineering teams coordinate complex change.