PinAppAI

MCP composition

Compose PinAppAI with the rest of your stack

Your AI editor is the integration runtime. PinAppAI brings change requests in. The other MCPs do the work — open a PR, ship a deploy, sync to Notion. Add them as you need them.

How this works

Your AI client is the integration runtime

Most feedback tools build a custom integration per destination — one for Slack, one for Linear, one for GitHub. Each one a fresh OAuth dance, a separate field-mapping UI, a maintenance treadmill. PinAppAI takes a different bet: your AI client (Claude Code, Cursor, Windsurf, Codex) is already the integration runtime. We ship an MCP server. So do GitHub, Vercel, Cloudflare, Linear, Notion, Stripe, and Figma. Install them alongside each other and your agent can read a change request and act on it — no per-platform plumbing on our side, no per-platform setup in our dashboard. The composition is the integration.

Building an MCP server?

It just works

PinAppAI is built on the open Model Context Protocol. Any MCP server installed in your AI client works alongside our change requests with zero PinAppAI-side configuration. If you ship an MCP and want it featured here, write to us.

Try it in your editor

Install @pinappai/mcp, mint an API key, and run /pinappai:fix-changes from Claude Code or Cursor.