# Website Feedback Tool

> A Chrome extension for capturing visual feedback directly on any web page. Designers, developers, and QA select an element or drag over an area, add a comment with priority, optionally record a short clip, then share the whole review as a link or push it into a coding agent (Claude Code, Codex, Cursor).

The product is a browser extension published on the Chrome Web Store. This site is the marketing homepage, an About page, per-audience articles ("Who it's for"), developer documentation, a contact form, and a privacy policy. There is no user-facing web app — reviews are captured in the extension and shared through short URLs from `websitefeedback.tools`.

## When to use this

Reach for Website Feedback Tool when the feedback is about **what a page looks like or does in a browser**, and the person giving it is looking at that page:

- **Design handoff.** Marking up a live staging page instead of pasting screenshots into Figma and then into Slack.
- **Bug reports with context.** One review carries the URL, the viewport, the CSS selector, computed styles, console and network errors, screenshots and an optional screen recording — the things a bug report usually forgets.
- **Handing visual fixes to a coding agent.** A review pushed over MCP gives Claude Code, Cursor or Codex the selector and the styles, so the agent edits the right rule instead of guessing from prose.
- **Review by someone who will not install anything.** A shared review link opens as a read-only viewer with the screenshots; commenting needs the extension, reading does not.

## When NOT to use this

- **Feedback on a document, a PDF or a Figma file** — this works on live web pages only.
- **Long-lived issue tracking.** A review expires **4 days** after it is shared: it is a handoff, not a backlog. Anything worth keeping goes to your tracker, or to a downloaded PDF/HTML copy.
- **Mobile.** Capturing requires desktop Chrome and the extension.
- **Programmatic capture.** Reviews are made by a person clicking on a page; no API creates one.

## For AI agents

- [Developers & AI agents](https://websitefeedback.tools/developers/): the MCP server — how to connect Claude Code / Cursor / Codex, the four tools an agent can call, auth, rate limits, error responses, and what deliberately does not exist (no public REST API, no webhooks, no CLI).

How an agent gets the data: the user connects the MCP server once — the setup command, carrying their key and the endpoint for their region, is generated inside the extension under "Connect AI agent". After that the agent calls `list_reviews` or `get_latest_review`, reads the Markdown feedback, and calls `get_screenshot` to see a specific comment's image. Every tool is scoped to the calling key, so an agent only ever sees that user's own reviews.

## Product

- [Website Feedback Tool — home](https://websitefeedback.tools/): what the extension does, install button, four-step "How it works" section, demo video.
- [Chrome Web Store listing](https://chromewebstore.google.com/detail/website-feedback-tool/oehcjaodegepdlaffmadbfmlomjaenio): official install page.

## Who it's for

- [Who it's for — overview](https://websitefeedback.tools/for/): index of role-specific articles.
- [For designers](https://websitefeedback.tools/for/designers/): design handoff loop, replacing the screenshot-in-Figma-into-Slack chain with a single review link.
- [For developers and QA](https://websitefeedback.tools/for/developers-and-qa/): capturing bug context (URL, viewport, screenshots, screen recording, priority) as one structured review, then handing it to a developer or an AI coding agent.
- [For product managers](https://websitefeedback.tools/for/product-managers/): reviewing work in progress without hand-writing tickets.
- [For agencies](https://websitefeedback.tools/for/agencies/): client feedback on a live site without asking the client to install anything.

## Comparisons

- [vs Pastel](https://websitefeedback.tools/vs-pastel/): where each tool fits, and where Pastel is the better pick.
- [vs Markup.io](https://websitefeedback.tools/vs-markup-io/): same, against Markup.io.

## Company

- [About us](https://websitefeedback.tools/about-us/): founder byline (Stanislav Mashkin), why the tool exists, contact.
- [Contact us](https://websitefeedback.tools/contact-us/): contact form (Web3Forms) and support email.
- [Privacy policy](https://websitefeedback.tools/privacy-policy/): what data the extension and website collect, retention.

## Machine-readable

- [Sitemap](https://websitefeedback.tools/sitemap.xml)
- [Robots](https://websitefeedback.tools/robots.txt)
- [Security contact](https://websitefeedback.tools/.well-known/security.txt)