PinAppAI

@pinappai/mcp · npm

Your reviewers’ words, inside Claude Code.

Install one MCP server. Your AI coding tool reads change requests, finds patterns, and proposes the fix, without leaving the editor. Works in Claude Code, Codex, Cursor, Claude Desktop, and Continue.

Get an API key →View on npm

Why MCP

Stop copy-pasting feedback into your editor

Without MCP, the loop is: open the dashboard, read the Inbox, copy the markdown, paste into Claude Code, ask it to fix. With MCP, you stay in the editor: the agent reads the Inbox itself, finds the patterns across reviewers, and proposes diffs you actually want to apply.

Install

Two commands. Any AI client.

`install` registers the MCP server in every AI client config it finds on your machine. `login` opens your browser for sign-in, picks a workspace if you have multiple, and saves a per-machine API key locally. No copy-paste of long JSON. No per-host snippets to keep in sync.

npx @pinappai/mcp install
npx @pinappai/mcp login

Auto-detected on:

  • Claude Code
  • Codex CLI
  • Cursor
  • Claude Desktop
  • Continue

Need a CI / headless install, or want the manual config? See the manual install →

Rather not install anything? Paste a URL into any client that speaks MCP over HTTP. See the hosted connector →

Workflows

Full workflows, one step

Workflows ship with the MCP, no extra setup. How you invoke one depends on your client: type /pinappai:apply in Claude Code, or ask Codex to “run the pinappai apply workflow”. Either way your agent runs the same procedure.

Your clientRun the apply workflow
Claude Code/pinappai:apply · type it. /pinappai: autocompletes the menu.
CodexAsk it: “run the pinappai apply workflow”. Codex has no slash menu for workflows; asking is the supported path and runs the same procedure.
Cursor/ · type it and pick the workflow from the menu.
Claude DesktopUse the + menu, then pinappai, then apply.
Any other MCP agentAsk in plain language, the same as Codex. The tools work everywhere.

Swap apply for any workflow below.

  • setup-project

    Walk through workspace + project + widget snippet + reviewers from scratch

  • embed-widget

    Embed the widget snippet into an existing project’s site and bootstrap the iteration marker

  • apply

    Drain the Inbox: edit source for every eligible CR (new, rejected, change-requested), then mark them applied in one atomic batch

  • generate-changes-page

    Generate the /changes/ review page for a multi-page batch of edits

  • remove

    Strip widget + /changes/ + helpers when you ship; preserves .pinappai/ for re-install

5 more in /docs/mcp/: analyze, summarize, audit-review, auth-help, reset-project.

Tools reference

38 tools: your agent calls these, you never type them

Your AI client calls these on your behalf. The 6 read tools below are what you’ll touch most often; the other 32 cover the apply loop plus project / workspace / member / reviewer lifecycle, gated by API-key role.

ToolPurpose
list_projectsList PinAppAI projects this API key can access
get_review_summaryCheap one-call summary of change-request state for a project
list_change_requestsPaginated change-request list with filters (status, page, reviewer)
get_change_requestFull CR detail with related[] siblings + optional inline screenshot
analyze_patternsServer-side groupings + heuristic clusters + optional AI clustering
get_screenshotInline screenshot as an MCP image content block

See the full list of all 38 tools →

FAQ

Common questions

What is MCP?

Model Context Protocol: an open standard so AI clients (Claude Code, Codex, Cursor, Continue, etc.) can talk to external data sources through a uniform interface. Read more at modelcontextprotocol.io.

Do I need to be a developer?

No. Workflows work for anyone using Claude Code, Codex, Cursor, Continue, or any MCP-aware agent. In Claude Code you type /pinappai:analyze; in Codex you just ask it to run the pinappai analyze workflow. Either way the AI does the rest.

Will it edit my code without asking?

No. Your AI client always confirms before applying any source edit. Every applies-to-source workflow (apply, remove) ends with an a/b/c/d picker (new branch, commit current, stage only, or skip), so commits never happen on autopilot. The MCP itself can mutate PinAppAI state (projects, members, CRs) when you ask it to, but it never touches your repo files directly.

What does it cost?

Free with any PinAppAI plan, including Free. The MCP just reads what you’ve already paid for.

Ready to bring your reviews into your editor?

Mint an API key, paste the install snippet, run a workflow. About 3 minutes start to finish.

Get started, free →Read on npm