Flip the loop around: your coding agent publishes its own work and hands you the review. It captures the build, gives you a link, waits for your flags, then pulls them back as structured JSON and revises — all over MCP. You do the one part agents can't: deciding.
Free to try — your agent can run a full review round on the free tier.
› build the pricing page and get it reviewed ● create_review("pricing v3") ↳ upload_url ready — pushing dist/ … ↳ review: app.comment.gg/s/pricing-v3-8a1c handed the link to Peter · awaiting feedback … ● get_feedback() ↳ 3 flags · 2 will-fix · 1 maybe /pricing → #plans .tier:nth-child(2) h3 "Change Pro to $14/mo, add 'billed annually'." ● add_version("pricing v4") ✓ flags carried forward GG — round closed. go next.
comment.gg gives your agent a small set of MCP tools that map exactly onto the review loop. It drives the whole thing and only ever waits on you for the human judgment call.
Add comment.gg to your agent once, over MCP. One endpoint, OAuth sign-in — no API keys to paste around.
Your agent calls create_review and uploads its real dist/ — not a screenshot — then hands you the review link.
It parks on await_feedback and watches the review live. You open it whenever you want.
You drop flags like any reviewer. The agent reads them with get_feedback — structured, with selector, text quote, and screenshot.
It fixes, then add_version pushes the next round into the same review. Your open flags carry forward automatically.
When you're happy, the round closes. Nothing left open, nothing lost between iterations. Go next.
comment.gg runs a remote MCP server. Add the endpoint to any MCP-capable agent, sign in once, and it can create reviews, push versions, and read your flags.
https://mcp.comment.gg/mcpOne command wires it up. Your agent signs in through your comment.gg account on first use.
Already building with comment.gg in your team's flow? The same review link works for humans and agents — bring people in too.
$ claude mcp add --transport http \ comment-gg https://mcp.comment.gg/mcp
// any MCP client — .mcp.json { "mcpServers": { "comment-gg": { "url": "https://mcp.comment.gg/mcp" } } }
Every flag comes back as JSON the agent can act on — the exact selector, the text it quoted, a screenshot, and your change request, verbatim. No re-typing what you meant. And when an agent is in the review, it shows up as itself — a flag marked “· agent,” never disguised as a human.
Get started free{ "status": "open", "page": "/pricing", "raisedBy": "Peter", "target": { "selector": "#plans .tier:nth-child(2) h3", "textQuote": "Pro — $12/mo", "screenshot": "https://…/flag-8a1c.png" }, "request": "Change Pro to $14/mo, add 'billed annually'." }
You shouldn't be the one taking screenshots and writing tickets back to your own agent. Hand it the review layer and just decide. GG — go next.
Get started free