Tyrekick MCP Server

What the code does

We read the source, 22 h ago · rules 3dff92dd89df

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.

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 -- npx -y tyrekick-mcp

{
  "mcpServers": {
    "tyrekick": {
      "args": [
        "-y",
        "tyrekick-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.tyrekick]
command = "npx"
args = ["-y", "tyrekick-mcp"]

{
  "mcpServers": {
    "tyrekick": {
      "args": [
        "-y",
        "tyrekick-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "tyrekick": {
      "args": [
        "-y",
        "tyrekick-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: 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 declared them in the registry entry; get the values from the project itself.