PAPI works in the tool you already use.
PAPI is an MCP server, not an app you switch to. It runs inside your AI client and keeps your project’s plan, decisions and history in one place no matter which client that is — or how many you use.
Confirmed working
Clients we have seen connect and run against a live project.
- Claude Code Runs locally
The most-used client to date, across 12 projects.
- Cursor Remote connection
Connected by an external user through the hosted OAuth flow.
- Codex Runs locally
Connected and ran tool calls against a live project.
- opencodeRuns locally
Connected and ran tool calls against a live project.
- zcodeRuns locally
Connected and ran tool calls against a live project.
Shipped, not yet exercised
We ship a working config for these and nobody has connected with one yet. Listed so the picture is complete, marked so it stays honest. If you get one running, tell us and it moves up.
- VS Code (GitHub Copilot)Remote connection
Config shipped and documented. No confirmed connection yet.
- WindsurfRemote connection
Config shipped and documented. No confirmed connection yet.
- Hermes AgentRemote connection
Config shipped and documented. No confirmed connection yet.
Anything else that speaks MCP
This list is not a gate. PAPI exposes a standard remote MCP server, so any client that can add one will connect — whether or not it appears above. Your own reasoning stays in your own client: PAPI never runs a model for you and never needs to know which one you use.
Missing a client you rely on? Tell us and we will get it documented.