1. Start the developer wizard
In the repo, run npx pincushion-mcp setup. It signs in, registers project URLs, and asks the developer to choose an editor explicitly. A report recipient uses npx pincushion-mcp claim <report-token> instead.
Everything the launch surface should answer in one place.
Pincushion lets stakeholders pin feedback on a live page while developers and AI agents pull that context into the repo over MCP. These docs cover the install path, current launch status, pricing, and where to go next.
Workflow overview
Each step narrows feedback into implementation instead of bouncing through screenshots and chat threads.
2. Restart and check feedback access
Restart the selected editor, then have the agent call get_actionable_pins. A config file alone does not prove that the agent is connected.
3. Review and approve a finding
Review an existing AI or human finding, approve that exact pin, and hand it to the developer or agent.
4. Use the extension when needed
The Chrome extension is optional. Install it when someone needs to place new browser pins; it is not required to connect an agent or read existing feedback.
Install flow
The launch path begins in the repo. Chrome remains an optional way to collect new browser feedback.
- Run npx pincushion-mcp setup from the repo and explicitly choose your editor.
- Restart the editor and ask the agent to call get_actionable_pins.
- Open /mcp for exact editor commands, including Codex CLI.
- Install the Chrome extension later only if you want to place new browser pins.
- Use /api for slash commands, CLI usage, and the supported tool surface.
- If you need help, use Support or email support@pincushion.io.
Pricing
The source of truth is simple: developers pay, stakeholders do not, and the free gate is projects rather than usage.
| Plan | What it includes | Price |
|---|---|---|
| Free | 1 project, unlimited pins and comments, full MCP workflow, stakeholders always free, 30-second cloud sync polling. | $0 forever |
| Pro | Unlimited projects, Realtime push, instant pin notifications, branch-per-page batching, priority email support. | $19/mo or $15/mo billed annually |
| Team | Everything in Pro, 3 developer seats included, role management, @mentions, extra seats at $12 per seat per month. | $49/mo or $39/mo billed annually |
Launch limitations
These are the public constraints the site and docs now reflect.
Chrome first
Chrome is the only public browser install path in this repo today. Firefox docs and store claims are intentionally deferred.
Privacy scope
The extension does not track browsing behavior; it sends only a few anonymous lifecycle events (installed, first activation, first pin — random ID, no URLs or page contents, opt-out in options). The marketing site uses Vercel Web Analytics and PostHog for pageviews and CTA events only. Full details in the privacy policy.
Billing policy
Subscriptions can be canceled any time and remain active through the end of the current billing period. There is no money-back guarantee claim on the public site.