Tyrekick runs on your own machine — the client starts it, so there is no endpoint to ping. 67 installs a week from npm. Last commit 16 Oct 2026.
Read and resolve human feedback pinned on your live prototype, straight from your coding agent.
What the code does
We read the source, 4 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
import { existsSync, readFileSync, writeFileSync, unlinkSync, readdirSync, statSync, mkdirSync } from "node:fs";
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add tyrekick -e 'TYREKICK_URL=<TYREKICK_URL>' -e 'TYREKICK_TOKEN=<TYREKICK_TOKEN>' -- npx -y tyrekick-mcp{
"mcpServers": {
"tyrekick": {
"command": "npx",
"args": [
"-y",
"tyrekick-mcp"
],
"env": {
"TYREKICK_TOKEN": "<TYREKICK_TOKEN>",
"TYREKICK_URL": "<TYREKICK_URL>"
}
}
}
}[mcp_servers.tyrekick]
command = "npx"
args = ["-y", "tyrekick-mcp"]
env = { TYREKICK_URL = "<TYREKICK_URL>", TYREKICK_TOKEN = "<TYREKICK_TOKEN>" }{
"mcpServers": {
"tyrekick": {
"command": "npx",
"args": [
"-y",
"tyrekick-mcp"
],
"env": {
"TYREKICK_TOKEN": "<TYREKICK_TOKEN>",
"TYREKICK_URL": "<TYREKICK_URL>"
}
}
}
}{
"servers": {
"tyrekick": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"tyrekick-mcp"
],
"env": {
"TYREKICK_TOKEN": "<TYREKICK_TOKEN>",
"TYREKICK_URL": "<TYREKICK_URL>"
}
}
}
}Put your own values in place of
<TYREKICK_URL> (Base URL of your deployed Tyrekick feedback worker (e.g. https://tyrekick-feedback.you.workers.dev)), <TYREKICK_TOKEN> (Bearer token for the worker's management routes (set via `wrangler secret put TYREKICK_TOKEN`)).
The author’s registry entry marks them as required.
Alternatives to Tyrekick
same job, measured the same wayRead, reply to and resolve website feedback threads from your coding agent.
Review comments pinned to a running frontend, read and resolved by your coding agent.
Production errors your coding agent can read: search, stack traces, context, trends, resolve.
Comments pinned on a website, as a queue your coding agent takes, fixes and resolves.
Stakeholders pin feedback on your live app; your AI agent reads the pins via MCP and fixes them.
Pin visual feedback on any live web page and send it to Claude Code, Cursor or your AI agent.
Read, reply to and resolve client feedback pinned on websites, PDFs, images and video.
Visual website feedback your coding agent applies: pin change requests on the live site over MCP.
Tyrekick — questions
Answers built from our own checks of this server.