A free alternative to Vercel toolbar comments, with agent access.
Vercel comments suit a team that already works in Vercel. pinthread works on any host, lets reviewers comment without a Vercel account, and hands feedback to your coding agent. Both tools support MCP.
At a glance
| pinthread | Vercel comments | |
|---|---|---|
| Where it works | Any website that loads the script tag, on any host or on localhost | Preview deployments by default. Production and localhost need the Vercel browser extension or the @vercel/toolbar package. |
| Who can comment | Anyone with link access, signed in with Google or as a named guest. Owners can limit a project to invited Google accounts. | Members of your Vercel team. On Pro and Enterprise, invited external users too. Everyone needs a Vercel account. |
| Price | Free plan at $0 a month | Included on all Vercel plans |
| Agent access | pinthread MCP server: list, read, reply to, start, resolve, and reopen threads with a project token | Vercel MCP toolbar tools list, read, reply to, and resolve threads. The vercel comments CLI command works from a terminal. |
| Where threads go | The pinthread dashboard, and a JSON download per project | The toolbar, email notifications, and optional Slack threads |
Checked on 10 October 2026. Sources: Comments overview, Toolbar in production, Vercel MCP toolbar tools, vercel comments CLI.
When Vercel comments fit better
- Your site and your whole team are already on Vercel.
- You want threads linked to Slack.
- You want comments on previews without adding code.
When pinthread fits better
- Your site runs on another host, or on your own server.
- Reviewers do not have, or should not need, a Vercel account.
- You want the same comments on localhost, previews, and production with one tag.
- Your coding agent should work through the feedback with a token for one project.
Switch from Vercel comments
- Sign up free and create a project for your site.
- Paste the script tag into your shared layout.
- Add each address where your site runs in the project's Settings.
- To match the Vercel setup, load the tag only on preview builds. Configuration shows how.
- Connect your agent. The agent guide has the setup for Claude Code, Cursor, and Codex.
<script src="https://pinthread.dev/embed.js"
data-project="YOUR_PROJECT_KEY" defer></script>Questions
Does pinthread work on Vercel?
Yes. Add the script tag to your root layout. The configuration page shows how to load it only on Vercel preview builds.
Do reviewers need an account?
No. On a project with link access, reviewers can comment as a named guest. A guest name is not a verified identity. Owners can restrict a project to invited Google accounts.
Can my coding agent read the comments?
Yes. Create an agent token in your project's Agent access tab, then connect Claude Code, Codex, Cursor, or another MCP client to https://pinthread.dev/mcp.
More comparisons
- pinthread vs AgentationA React toolbar for your own notes, with a local MCP server.
- pinthread vs Agentation (feature by feature)Feature-by-feature breakdown of setup, annotation modes, storage, and agent access.
- pinthread vs Marker.ioBug reports with screenshots, console logs, and session replay. Paid plans after a 15-day trial.
- pinthread vs BugHerdClient feedback as tasks on a project board. Paid plans after a 7-day trial.
- pinthread vs UserbackUser feedback and bug reports. Free plan locks feedback after 7 days.
- pinthread vs PastelWebsite annotations on canvas proxy links. Free plan allows one active canvas.
- pinthread vs RuttlVisual feedback and live CSS edits. Free plan caps projects and video comments.
- pinthread vs React GrabDevelopment-time React source context, copied or sent to coding agents.
- pinthread vs FeedbucketAgency feedback with screenshots, video, integrations, and MCP.
- All alternativesFree plans, prices, and agent access in one table.
- Agent workflow guideSet up Claude Code, Cursor, or Codex to resolve comments.