Skip to content

Claude Desktop TokenZero audit_repo_token_waste

How to: Claude Desktop TokenZero audit_repo_token_waste

client:Claude Desktop transport:streamable-http tool:audit_repo_token_waste

Add TokenZero to Claude Desktop

  1. 01

    Open ~/Library/Application Support/Claude/claude_desktop_config.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.tokenzero.sh/mcp"
      ]
    }
  }
}
  1. 02

    Save the file and restart Claude Desktop.

  2. 03

    Ask for something audit_repo_token_waste does. Claude Desktop lists the server's tools on connect and calls audit_repo_token_waste itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that TokenZero's identifier in your config matches the one above exactly.

Claude Desktop has no remote transport in its config file, so this bridges through mcp-remote. Restart the app after saving. Claude Desktop docs

Set these first

TokenZero will not start until these are set, so audit_repo_token_waste never becomes available.

  • TOKENZERO_URL
  • TOKENZERO_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 26 October 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.