PAPI + Cursor

PAPI connects to Cursor over MCP. The plan, the decisions, and the direction sit in the same chat as the code, so a quick pivot doesn't quietly bend the project off course.

Connect PAPI See what PAPI does

Free on three projects · no card · 14-day refund on Pro

How PAPI fits Cursor

No new app to open: PAPI runs inside the AI tool you already build in. One file in .cursor/mcp.json and PAPI's tools appear in Cursor's chat. Run orient at the top of a session and Cursor answers with the live state: what shipped, what stalled, what needs you.

Decisions on the record: every call your project makes is kept, with the why, and checked against new work. Cursor sessions tend to be short and many. Every call stays on the record between them, so the tenth chat opens as grounded as the first.

Catches drift: the moment new work slides off the plan, PAPI flags it. Tab-speed edits add up. Each build lands against a scoped handoff with acceptance checks, so fast changes still get checked against the plan.

Connect PAPI to Cursor

Create your account. Sign in at getpapi.ai with GitHub or email and name your first project.
2
Add the config file. Save this as .cursor/mcp.json in your project root, or ~/.cursor/mcp.json for every project. Cursor opens a browser tab to sign you in on first connect.
.cursor/mcp.json
```
{
  "mcpServers": {
    "papi": {
      "url": "https://mcp.getpapi.ai/mcp"
    }
  }
}
```
Run setup in chat. In Cursor's chat, ask it to run setup. PAPI writes your product brief, then plan starts your first cycle.

Questions

My rules files already hold the context.: Files describe. They don't decide. Nothing checks the finished work against them, and they never reorder the backlog when reality changes.
Can't I just use Linear or Jira?: They're built for teams of humans, and they sit in a tab your AI can't see. PAPI runs inside the tool you build in, so the plan and the work stay in one conversation. Different category; keep Linear if your team lives there.
Does PAPI read my code?: Your code stays on your machine. PAPI adds a planning layer to whatever you're already building, it doesn't read your source.
Does the same project work from Claude Code too?: Yes. PAPI is one remote MCP server, so the same project connects from Claude Code, Cursor, Codex, or any MCP tool, and every session picks up the same plan.