Tyrekick

What tyrekick MCP server does

The tyrekick MCP server gives a coding agent access to human feedback collected from a live web page. Reviewers place pins on page elements and write comments in the browser. The agent can then retrieve those comments with their surrounding context, work through the requested changes, and mark completed items as resolved.

Each feedback item can include the element's visible text, the nearest section heading, route, viewport, and uncaught page errors. This context helps an agent locate the relevant UI and distinguish a functional issue from a visual or content request. The browser widget sends feedback to a destination chosen by the project owner; Tyrekick does not provide a central backend or account system.

How it works

The usual deployment uses the Tyrekick widget on the prototype and a Cloudflare Worker as the destination. The widget posts reviewer comments to that Worker, while the MCP process reads and updates the stored feedback through the Worker endpoint. A JSON transport can also point to another endpoint that accepts and persists the feedback payload.

The agent loop uses five tools: list_feedback, get_feedback, triage_feedback, resolve_feedback, and feedback_stats. A typical request is to list open feedback, fix the reported problems, and resolve each item with a note. Resolution updates the review state so the reviewer can see that the pin was addressed.

Setup and configuration

Install the MCP process with the package command used by the example configuration:

claude mcp add tyrekick \
  --env TYREKICK_URL=https://your-worker.example.workers.dev \
  --env TYREKICK_TOKEN=your-token \
  -- npx tyrekick-mcp

TYREKICK_URL identifies the deployed feedback destination, and TYREKICK_TOKEN authenticates requests. The Worker token is created as a secret on the destination. The browser widget must also be installed on the prototype and configured to send feedback to that destination. The Tyrekick MCP server is intended for the worker-based agent loop described in the project documentation.

Tools and capabilities

The tyrekick MCP server provides:

• Open-feedback listing for reviewing outstanding comments.
• Individual feedback retrieval for inspecting a specific report.
• Triage operations for classifying or organizing feedback.
• Resolution operations that close a report and attach a note.
• Feedback statistics for checking review state counts.

Feedback can describe the exact page element and include visible text, location context, viewport information, and page errors. The surrounding browser widget supports threaded comments and lets reviewers see when an item has been resolved.

Limitations and notes

The MCP process does not itself host the review page, store feedback, or provide reviewer accounts. Those responsibilities belong to the widget and the destination configured by the project owner. The documented quickstart uses Discord for basic delivery, but the full agent workflow requires the Worker destination with persistence and MCP access.

Shared review is available through a review key, but the key is embedded in the page and can be read by anyone who can open the prototype. That mode therefore suits private review links rather than unrestricted public pages. Reviewer identity is not scoped by individual accounts, and the project owner is responsible for securing the destination and token.