Install Guide

Get started with PAPI

Connect PAPI to your AI coding tool. Run your first cycle plan in under 5 minutes.

Your code stays on your machine. PAPI adds a planning layer to whatever you're already building, it doesn't read your source.

Prerequisites

An MCP-compatible AI tool. Claude Code, Cursor, VS Code (Copilot Chat), Windsurf, OpenCode, Amazon Q CLI, or any tool supporting the MCP protocol.

A browser to sign in. On first connect your tool opens a browser tab so you can sign in. That is the whole setup. No local server, no Node, no token to copy.

2. Connect your tool

Pick your AI coding tool and copy its config. Every tool uses the same connector link and signs you in through your browser on first connect. Paste it as-is.

Paste into Claude Code chat

Add PAPI as an MCP server for this project. Run this from the project root:

  claude mcp add --transport http papi https://mcp.getpapi.ai/mcp

The server is added but NOT yet authenticated — only you can finish this, in a browser. After the command succeeds, tell me exactly this:
"PAPI is added. Sign in to connect it: run  claude mcp login papi  (Claude Code v2.1.186+) and approve in the browser — or run /mcp, choose papi, pick Authenticate. Sign in with the same account you used on getpapi.ai."

Paste this as a chat message in Claude Code. Claude Code installs PAPI itself, opens a browser tab so you can sign in, and then runs setup. No terminal, no token to copy.

3. First run

After saving your config, restart your MCP client. Then in your AI tool, run these three commands in order:

setup

Initialises PAPI for your project. Generates a Product Brief and scaffolds your workflow.

plan

Generates your first cycle plan: scoped tasks with full BUILD HANDOFFs, ready to build.

build_list

Shows the tasks queued for this cycle. Pick one and start building.

Expected time: install to first plan in under 5 minutes.

What's next

Tool reference →

Every PAPI tool, what it does, and when to use it.

Dashboard →

View cycles, tasks, build reports, and decisions at getpapi.ai.

Add another project →

Go to Portfolio, then New Project. The same connector link covers every project you own.

Discord →

Get help, share feedback, see what others are building.

Troubleshooting

PAPI tools not appearing

Restart your MCP client after pasting the connector, so it re-reads the config. On first connect your tool opens a browser tab to sign you in. Finish that sign-in, then check the tools list again.

The sign-in tab never opened

Some tools only open the sign-in tab when you first call a PAPI tool. Ask your AI to run setup, or check your tool has a browser handler enabled. If it still does not appear, re-paste the connector and restart the client.

Stale .mcp.json from a previous setup

Open .mcp.json and delete only the "papi" entry inside the mcpServers object. Keep the file and any other MCP servers (github, supabase, etc.) intact. Then paste the fresh papi entry from your install snippet. NEVER delete .mcp.json, other MCP servers share it.

Stuck install, nothing connects no matter what

Open getpapi.ai/settings, find your project, and click "Reset connection" for a fresh install snippet. Your project data, cycles, and history are preserved. Replace the papi entry in your .mcp.json with the new snippet and restart your MCP client.

Using a token-based tool (Zed, z.ai) and it will not connect

Open getpapi.ai/settings, find your project, and copy the token snippet from the "Advanced" panel. That is the only case where a connection token is needed. Paste it in place of the URL-only config and restart your client.

Want to start execution over but keep your strategy