Workflow overview
Each step narrows feedback into implementation instead of bouncing through screenshots and chat threads.
1. Install the extension, or don't
Stakeholders and reviewers install the Chrome extension, enter their name and email, and pin directly on live or staging pages. Or skip the install: share a project's public report link and reviewers can view it, reply, and drop pins right in the browser, no extension, no account.
2. Register the project
Developers connect the MCP server in their IDE and run configure_project once so the extension auto-activates on local and deployed URLs.
3. Review and approve pins
Open pins stay attached to the relevant page. Teams can comment, approve implementation, and hand work to a developer or agent.
4. Implement with MCP
Claude Code, Cursor, VS Code, Windsurf, and Antigravity can pull approved pins, claim work, ship the change, and resolve the feedback thread.
Install flow
The launch path stays simple: one gate for Chrome, one docs surface for setup, and one support path if anything breaks.
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.
Next steps
Install the extension gate first, then finish your MCP setup in the IDE-specific docs. If you are already live in the repo, the fastest path is /mcp followed by /api.