pincushion

Pincushion for Claude Code.

Visual feedback that lands in your IDE. Reviewers pin feedback from a link, no account needed; your Claude Code agent reads them via MCP — selector, DOM snippet, screenshot, viewport, thread, project context, and acceptance criteria — and ships the change from inside your editor.

Install Pincushion for Claude Code See the full product →

The flow

  1. A reviewer pins feedback from a link, no account needed. On your own app, the Chrome extension or snippet lets them pin any element.
  2. You open Claude Code in your repo, run /pins or /implement
  3. Claude reads the pin's full work packet via MCP — selector, DOM snippet, screenshot, viewport, thread, project context, and likely files
  4. Claude makes the change, calls fix_and_resolve with branch + PR URL
  5. Deploy hook auto-resolves the pin on production. Pincushion AI verifies the fix on the next deploy and records the verdict

Connect Claude Code

Start with npx pincushion-mcp setup to sign in, register project URLs, and explicitly choose Claude Code. From inside your project, you can also run:

claude mcp add pincushion -- npx pincushion-mcp --project-dir .

Restart Claude Code, then ask it to call get_actionable_pins. Configuration does not prove the agent is connected. No pins yet? Ask the agent to call start_quickstart_demo to try the loop on a throwaway demo page, or run /critique <your-url> so Pincushion AI drops its first pins on your site. Approve one pin, then ask the agent to implement it. The Chrome extension is optional and only needed to place new browser pins.

For a Crit report, use npx pincushion-mcp claim <report-token> to resume configuration after authenticated project access is confirmed.

Slash commands available after install

Existing feedback arrives as an agent-ready task with the selector, DOM, screenshot, viewport, and thread in one MCP call.

Install Pincushion for Claude Code Back to home