pincushion

Hand visual feedback to your AI coding agent over MCP.

An agent can only fix what it can locate. "The header looks off" in a chat message gives it nothing to grep for. A Pincushion pin is an agent work packet: the page URL, the element's CSS selector, a DOM snippet, a screenshot, the viewport and the full thread.

The handoff, step by step

  1. Humans pin the live page. The builder uses the Chrome extension or the widget script tag. Reviewers join through an invite link as free commenters. Every pin captures the work packet at click time.
  2. Connect your agent. Add the Pincushion MCP server to Cursor, Claude Code, Codex, Windsurf or Copilot. See the MCP page and the docs for setup.
  3. Approve what should be built. Only approved pins are meant for implementation, so an unreviewed opinion never reaches the agent as a task.
  4. The agent reads the packets. implement_approved_pins returns approved pins grouped by page, with selectors and a suggested branch name. get_actionable_pins lists everything waiting for attention.
  5. Claim, fix, resolve. claim_pin marks a pin as in progress. After the change, fix_and_resolve closes it with the commit SHA, branch and PR URL, and the pin shows that trail to reviewers.

When the agent needs more

The agent can ask a question on the pin with add_agent_reply, so the reviewer answers in the same thread instead of a side chat. You can also send a single pin straight to a local agent with assign_pin_to_agent.

Related: what a visual feedback MCP server does, how agents fix UI feedback and browser agent to coding agent.

Start free

Pincushion's free tier covers one project with unlimited manual pins and 25 AI actions a month, and every new account starts with a 14-day full-Pro trial. Commenters are always free. See pricing for the details.

Sign up free Get a free crit of your page