PinAppAI

Composes with @pinappai/mcp

Pin a change. Get a PR.

Install @pinappai/mcp alongside the official GitHub MCP server in Claude Code or Cursor. Run /pinappai:fix-changes and your agent reads the queue, edits the right files, and opens a pull request — without leaving the editor.

Get an API key → GitHub MCP repo

How it composes

Two MCPs, one workflow

PinAppAI exposes change requests, screenshots, and pattern analysis as MCP tools. The official GitHub MCP server exposes file reads, file writes, branch creation, and pull request management. Your AI client connects to both. When you ask “fix the queued change requests,” it reads from PinAppAI, plans the edits, finds the files in your repo, makes the changes, and opens the PR — all in one prompt run, with your hand on the approval at every step.

Install

Three steps

  1. 1. Install @pinappai/mcp

    Mint an API key in your workspace and add the MCP to your client. Snippets for Claude Code, Cursor, Continue, Codex, and Claude Desktop are on the install page.

    Install @pinappai/mcp →

  2. 2. Install the official GitHub MCP

    GitHub publishes github-mcp-server (Go). The README shows OAuth and PAT setup for stdio and remote modes. Use the same MCP install pattern your AI client expects.

    github/github-mcp-server →

  3. 3. Run /pinappai:fix-changes

    In Claude Code or Cursor, type /pinappai:fix-changes. Your agent will list pending change requests, group them, and propose edits — and use the GitHub MCP to open the PR when you approve.

A typical flow

From pinned comment to merged PR

  1. A reviewer pins on the live site

    They highlight a heading that should change, dictate the new copy, and submit. The change request lands in the PinAppAI queue with the locator, the screenshot, and the original wording.

  2. You run /pinappai:fix-changes in Claude Code

    Claude lists open CRs (via @pinappai/mcp), groups duplicates, and shows you the plan. You approve the batch you want to ship.

  3. The agent edits the repo

    For each approved CR, Claude finds the relevant file via the GitHub MCP, edits it, and stages the change. You see every diff before it commits.

  4. A pull request opens

    The GitHub MCP opens a branch, commits, and creates a PR with the original screenshots from PinAppAI in the description. Reviewers see what the user saw.

  5. Merge ships the change

    Your normal CI/preview-deploy flow runs. On merge, the CR is transitioned to “done” via @pinappai/mcp — the original reviewer can be notified.

Coming next

Native one-click GitHub from the dashboard

Today the composition runs in your AI editor. We are building a server-side version that runs from the PinAppAI dashboard — connect GitHub once, and PinAppAI’s own agent ships the change. Marketing managers will be able to drive the loop without an editor. If you want early access, write to us.

Try the composition today

Install both MCPs and run /pinappai:fix-changes from Claude Code or Cursor.

Install @pinappai/mcp → GitHub MCP on npm