What it does
PAPI connects to AI coding tools over MCP and keeps a single project plan that every teammate's AI works from. Work moves through four steps: plan the next batch of tasks, build them one at a time, review the change against team rules and tests, and release with a record of who built what, with which AI, and when. Each person can use a different tool. The site names Claude Code, Cursor, ChatGPT, Codex and Lovable, and says any MCP client works. Decisions, conventions and build reports persist between sessions, so a new chat starts from the project's current state rather than from zero. PAPI says it runs no AI of its own and never sees source code; it stores tasks, decisions and build reports, and model costs come through the AI tool you already use. A shared board updates as tasks move, and optional switches cover things like automatic branches, commits, pull requests, a PR reviewer and a security scan.
Capabilities
- Plan, build, review and release cycles shared across a team
- Build handoffs and decision memory that persist across sessions and tools
- Works with any MCP client, including Claude Code, Cursor, ChatGPT and Codex
- Live task board
- Optional automatic branch, commit, pull request and PR review steps
When to use it
- Teammates use different AI coding tools but need to work from one plan
- You lose context when you start a new AI chat on the same project
- You want a record of which AI built each change in a release
Alternatives to explore
- Linear
- Plane
- monday.com
- Paperclip