Claude Code TokenLab MCP Server compare_tokenlab_models
How to: Claude Code TokenLab MCP Server compare_tokenlab_models
Add TokenLab MCP Server to Claude Code
-
01
Run this in your project directory.
claude mcp add tokenlab -e TOKENLAB_API_BASE=<TOKENLAB_API_BASE> -e TOKENLAB_API_KEY=<TOKENLAB_API_KEY> -e TOKENLAB_REQUEST_TIMEOUT_MS=<TOKENLAB_REQUEST_TIMEOUT_MS> -e TOKENLAB_MCP_TOOL_PROFILE=<TOKENLAB_MCP_TOOL_PROFILE> -e TOKENLAB_MCP_SCHEMA_MODE=<TOKENLAB_MCP_SCHEMA_MODE> -e TOKENLAB_MCP_MAX_FILE_BYTES=<TOKENLAB_MCP_MAX_FILE_BYTES> -e TOKENLAB_MCP_INLINE_BYTES=<TOKENLAB_MCP_INLINE_BYTES> -e TOKENLAB_ARTIFACT_DIR=<TOKENLAB_ARTIFACT_DIR> -e TOKENLAB_MANAGEMENT_TOKEN=<TOKENLAB_MANAGEMENT_TOKEN> -- npx -y @tokenlabai/mcp-server
-
02
Restart your session so the server is picked up.
-
03
Ask for something compare_tokenlab_models does. Claude Code lists the server's tools on connect and calls compare_tokenlab_models itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that TokenLab MCP Server's identifier in your config matches the one above exactly.
Adds it for this project only. Append --scope user to make it available everywhere. Claude Code docs
Set these first
TokenLab MCP Server will not start until these are set, so compare_tokenlab_models never becomes available.
-
TOKENLAB_API_BASE -
TOKENLAB_API_KEY -
TOKENLAB_REQUEST_TIMEOUT_MS -
TOKENLAB_MCP_TOOL_PROFILE -
TOKENLAB_MCP_SCHEMA_MODE -
TOKENLAB_MCP_MAX_FILE_BYTES -
TOKENLAB_MCP_INLINE_BYTES -
TOKENLAB_ARTIFACT_DIR -
TOKENLAB_MANAGEMENT_TOKEN
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 18 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.