Tag-per-Track MCP Server

What the code does

We read the source, 2 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.

        const entries = await fs.promises.readdir(dir, { withFileTypes: true });

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 tag-per-track-mcp -- npx -y tag-per-track-mcp

{
  "mcpServers": {
    "tag-per-track-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tag-per-track-mcp"
      ]
    }
  }
}

[mcp_servers.tag-per-track-mcp]
command = "npx"
args = ["-y", "tag-per-track-mcp"]

{
  "mcpServers": {
    "tag-per-track-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tag-per-track-mcp"
      ]
    }
  }
}

{
  "servers": {
    "tag-per-track-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "tag-per-track-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: TAG_PER_TRACK_API_KEY (Studio API key (tpt_live_...) generated on https://tag-per-track.cloud. Consumes prepaid credits, no crypto wallet needed. Takes priority over the wallet mode), WALLET_PRIVATE_KEY (Private key of a dedicated Base burner wallet (66 hex chars starting with 0x) for USDC micro-payments via x402. Used only when no API key is set), MAX_SPENDING_USDC (Client-side spending cap per request in USDC (wallet mode)), TAG_PER_TRACK_NO_PERSIST (Set to 1 or true to keep API-key analyses out of your dashboard history).