Pincushion
Wire live-app stakeholder pins into your coding agent so feedback becomes actionable fixes without copy-pasting screenshots.
Overview
Pincushion MCP is a MCP server for the Build phase that lets your agent read stakeholder feedback pinned on your live app so it can implement fixes from real UI context.
What is this MCP server?
- Stakeholders pin feedback directly on the live application UI
- MCP bridge lets the coding agent read pinned issues in context
- Closes the loop from review comment to code change in one toolchain
- npm stdio package pincushion-mcp (v1.3.1)
- Designed for agent-first fix workflows, not static ticket exports
- Server version 1.3.1
- npm package identifier pincushion-mcp
- stdio MCP transport
What problem does it solve?
Feedback on staging or production gets trapped in chats and screenshots, so your agent never sees precise, in-context issues on the page you shipped.
Who is it for?
Solo builders or tiny teams running preview or production URLs where non-technical stakeholders mark up the app while you code in an MCP agent.
Skip if: Pure local-only CLI projects with no deployed UI or teams that want a full issue tracker replacement without the Pincushion product workflow.
What do I get? / Deliverables
Pinned comments flow into MCP tools so the agent can fetch feedback and ship fixes without manual re-description of every UI bug.
- Agent-readable pinned feedback from the live application
- Structured input for implementing UI and copy fixes
- Reduced manual transfer of review notes into the IDE
Recommended MCP Servers
Journey fit
Canonical shelf is Build because the loop assumes a running app and turns annotated feedback into implementation work. PM subphase captures stakeholder input, triage, and agent-driven fix workflows rather than pure CI or security.
How it compares
Live-app feedback MCP bridge, not a generic GitHub issue or code-review skill.
Common Questions / FAQ
Who is Pincushion MCP for?
Builders who ship web apps and want clients or teammates to pin UI feedback that Claude Code, Cursor, or similar agents can read and act on.
When should I use Pincushion MCP?
Use it during active build and iteration when you have a deployed app and need stakeholder comments to drive agent-led fixes.
How do I add Pincushion MCP to my agent?
Add the pincushion-mcp npm package as a stdio MCP server in your agent config and complete setup with the Pincushion plugin workflow on your live app.