Yandex Tracker MCP Server

What the code does

We read the source, 2 d ago · rules ccca72095570

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.

const child = spawn(process.execPath, [script, ...process.argv.slice(3)], {

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

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

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

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

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

This one needs environment variables set before it will start: TRACKER_TOKEN (OAuth-токен Яндекс 360 (y0_...) или IAM-токен Yandex Cloud (t1....)), TRACKER_ORG_ID (ID организации (Яндекс 360 или Yandex Cloud)), TRACKER_AUTH (Схема авторизации: oauth (Яндекс 360) или iam (Yandex Cloud)). The author declared them in the registry entry; get the values from the project itself.