Describe what you want to build and Claude creates the project in AxioPlan: epics, PERT-estimated tasks, dependencies and a team. AxioPlan's engines do the maths, so the timeline, cost and P85 delivery date stay right every time you or Claude change something.
Claude handles the conversation; AxioPlan does the scheduling, estimating and staffing. Every answer comes from the live plan, not from Claude's guesswork.
“Plan a customer portal rebuild: SSO, billing history and a support inbox. Two backend devs, one frontend, one QA. Deadline end of March.”
“Break the mobile app epic into tasks with sizes and risk, and wire the dependencies.”
“What's the P85 delivery date, and what does the project cost?”
“What's on the critical path, and which tasks have no one assigned?”
“If you let it hire as needed, when does the project actually finish?”
“Add a two-week hardening phase before launch and put Ana on it.”
“Push everything after the API work out by a week.”
“Cut the reporting epic. How much earlier do we ship?”
Copy your connector URL from AxioPlan, then in Claude open Settings → Connectors → Add custom connector and paste it. Works in Claude on the web and Claude Desktop.
Claude opens AxioPlan's consent screen. Choose whether Claude can only read your plans, edit them, or also delete projects. You can revoke access any time.
Claude creates the project, epics, estimated tasks and dependencies. The plan lands in AxioPlan with effort, cost and confidence dates already calculated.
Keep editing in Claude or on the Gantt chart, let the allocation engine staff it, share a read-only link with a client, and export the plan to Jira.
AxioPlan is a remote MCP server secured with OAuth 2.1. Claude gets fifteen tools, grouped into three permission levels you approve when you connect. Every edit runs in a single transaction, so a plan is never left half-changed.
Common questions about planning projects with Claude and AxioPlan.