Skip to content
ReviewRamble

The weekly brief

AI, reviewed, in your inbox.

  • New reviews of tools, models, MCP servers and repos, with the verdict up front
  • Re-checked prices and ratings when something changes
  • New analysis pieces as they are published

Models, agents, MCP servers and the tools actually worth your time.

One email a week. Unsubscribe with the link in any brief. How we use your email

TagLoop

Hosted MCP server and Chrome extension that let you click page elements, comment and send the feedback straight back to your coding agent.

Reviewed by ReviewRamble editors · Updated

Setup docs Free

Our rating

3.5/5

A thoughtful answer to the agent that says the layout is fixed when it is not, held back by being a one-person hosted service with 6 users.

What is TagLoop?

TagLoop closes the loop between a coding agent and the person who has to look at its work. The agent calls request_tagloop_feedback with a checklist of URLs and instructions; you open the page in Chrome, pick elements in the TagLoop DevTools panel, type or dictate comments, answer multiple-choice questions and attach screenshots or mock-ups; the result goes back to the agent with each element's CSS selector, XPath, tag, attributes and visible text, so it can find the source to change.

It is a hosted service, not a package: the MCP endpoint is https://tagloop.dev/mcp over HTTP, with OAuth sign-in for Claude Code, Codex, ChatGPT, Cursor, Gemini CLI, OpenCode and Antigravity, and a tgl_ API key for PhpStorm. It exposes 5 tools, including remote review mailboxes that clients or QA staff can use with a share code and no account. The service is run by Paweł Kania (AQUASITE.PL) in Zielona Góra, Poland.

The code is not open source; a self-hosted Docker build is available under licence on request. Note that tagloop.com is a parked domain; the product lives at tagloop.dev. The Chrome Web Store listing showed 6 users and extension version 1.0.6, updated 26 September 2026.

How to install TagLoop

https://tagloop.dev/mcp

Is TagLoop worth it?

TagLoop solves a real gap in agent coding. An agent can run tests and take screenshots, but it cannot tell that a button looks wrong to a person. TagLoop lets it ask: the call blocks while you click the offending element and say what is off, and the answer arrives as selectors and structured fields rather than prose the agent has to interpret. Questions with fixed answers go further, returning a stable id such as keep or drop instead of a paragraph.

The data handling is better than the size of the project suggests. The extension sends nothing until you submit, password, token and payment fields are blanked before capture, and on the hosted instance results and screenshots are deleted after 1 hour, with interactive reviewer codes expiring after 48 hours. API keys and OAuth tokens are stored only as hashes, images are served through signed links, and the privacy policy says review data is not sold or used to train models. Voice notes go from your browser to Groq under your own key and never reach TagLoop.

Prompt injection is the obvious exposure, because a reviewer's comment is text that a coding agent will act on. That matters most for remote mailboxes, where anyone holding a share code can submit. TagLoop flags suspicious feedback in the result, and calls the check a best-effort tripwire, not a guarantee. Your agent should still treat comments as instructions from an untrusted reviewer.

The catch: you are relying on a hosted server from a single operator, with no published pricing, no service-level terms and code you cannot inspect. Feedback, page URLs, screenshots and your reviewers' comments all pass through tagloop.dev, and the terms say the service may change or be discontinued. A team that cannot send screenshots of an unreleased product to a third party has to ask for the self-hosted build.

Our take: TagLoop is worth an afternoon for a solo developer or a small agency doing front-end work with agents; for anything confidential, open-source element pickers that run locally are the safer starting point until TagLoop has more users and published terms.

Where it earns its place

  • A freelance developer building a marketing site with Claude Code

    Tell the agent exactly which spacing and colours are wrong after each pass

    The agent ends each change by calling request_tagloop_feedback with the pages it touched; you click each problem element and dictate a note. It replaces screenshots pasted into chat, and costs nothing on the hosted service.

  • A three-person agency running client sign-off rounds

    Collect a client's comments on a staging site without giving them an account

    Create a remote review mailbox, send the client a share code, and let a webhook tell the agent when feedback arrives. Treat client comments as untrusted text before the agent acts on them.

  • A product designer choosing between layout options with an agent

    Make a quick decision on three variants without writing a brief

    The agent asks a single-choice question pinned to the element, such as keep, narrow or remove, and gets back the chosen id. One click replaces a round of written back-and-forth.

Before you commit

Setup
Install the Chrome extension and sign in from its settings, then add https://tagloop.dev/mcp to the client (for Claude Code, claude mcp add --transport http tagloop https://tagloop.dev/mcp) and authenticate. An optional skill teaches the agent when to ask for a review. A few minutes to the first review.
Integrations
5 tools: request_tagloop_feedback (blocks until the reviewer submits), create_tagloop_remote_review, fetch_tagloop_feedback, close_tagloop_review and get_tagloop_help. HMAC-signed webhooks notify on new feedback. Documented for Claude Code, Codex, ChatGPT, Cursor, Gemini CLI, OpenCode, Antigravity and PhpStorm.
Data and privacy
On submission the extension sends the page URL and title, element selectors, attributes and visible text, comments, screenshots, screen resolution and browser version to tagloop.dev; sensitive input fields are blanked first. Results expire after 1 hour. The server cannot read your code or conversation, only what tools send it. Not used for training per the privacy policy. Reviewer comments can carry prompt injection.
Cost at scale
No prices are published for the hosted service. Image storage is capped per user and per session; self-hosting (Postgres, web app, MCP gateway and nginx in Docker Compose) is licensed on request.
Limits
Requests wait for a person, so they can time out; a retry with the same session id resumes. Up to six reference images per comment. Idle connections close after six hours. Small user base, so client-specific bugs may surface first for you.

What’s good

  • Feedback returns as selectors and structured fields
  • Multiple-choice questions give agents unambiguous answers
  • Results and screenshots deleted after 1 hour
  • OAuth for most clients; no local install for the server

What’s not

  • Hosted by a single operator; code not open source
  • No published pricing or service commitments
  • Reviewer comments are a prompt-injection channel
  • Chrome only, through a DevTools panel

Best for

Solo developers and small agencies who build front ends with Claude Code, Codex or Cursor and want to point at what is wrong instead of describing it.

TagLoop alternatives

TagLoop: common questions

Is TagLoop worth it?
A thoughtful answer to the agent that says the layout is fixed when it is not, held back by being a one-person hosted service with 6 users. We rate it 3.5 out of 5.
How much does TagLoop cost?
Free to register for the hosted service; no paid plans are published. Self-hosted licences are quoted on request.
What are the downsides of TagLoop?
Hosted by a single operator; code not open source; no published pricing or service commitments; reviewer comments are a prompt-injection channel; chrome only, through a DevTools panel.
Who is TagLoop best for?
Solo developers and small agencies who build front ends with Claude Code, Codex or Cursor and want to point at what is wrong instead of describing it.
How much does TagLoop cost for a team or in production?
No prices are published for the hosted service. Image storage is capped per user and per session; self-hosting (Postgres, web app, MCP gateway and nginx in Docker Compose) is licensed on request.
Is TagLoop safe for company data?
On submission the extension sends the page URL and title, element selectors, attributes and visible text, comments, screenshots, screen resolution and browser version to tagloop.dev; sensitive input fields are blanked first. Results expire after 1 hour. The server cannot read your code or conversation, only what tools send it. Not used for training per the privacy policy. Reviewer comments can carry prompt injection.
What are the best TagLoop alternatives?
The closest alternatives we have reviewed are Chrome DevTools MCP and Playwright MCP.

Answers checked Nov 11, 2026.