Gemini CLI TokenLab MCP Server Resource/TokenLab Model Explorer
How to: Gemini CLI TokenLab MCP Server TokenLab Model Explorer
Add TokenLab MCP Server to Gemini CLI
-
01
Open ~/.gemini/settings.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"tokenlab": {
"command": "npx",
"args": [
"-y",
"@tokenlabai/mcp-server"
],
"env": {
"TOKENLAB_API_BASE": "<TOKENLAB_API_BASE>",
"TOKENLAB_API_KEY": "<TOKENLAB_API_KEY>",
"TOKENLAB_REQUEST_TIMEOUT_MS": "<TOKENLAB_REQUEST_TIMEOUT_MS>",
"TOKENLAB_MCP_TOOL_PROFILE": "<TOKENLAB_MCP_TOOL_PROFILE>",
"TOKENLAB_MCP_SCHEMA_MODE": "<TOKENLAB_MCP_SCHEMA_MODE>",
"TOKENLAB_MCP_MAX_FILE_BYTES": "<TOKENLAB_MCP_MAX_FILE_BYTES>",
"TOKENLAB_MCP_INLINE_BYTES": "<TOKENLAB_MCP_INLINE_BYTES>",
"TOKENLAB_ARTIFACT_DIR": "<TOKENLAB_ARTIFACT_DIR>",
"TOKENLAB_MANAGEMENT_TOKEN": "<TOKENLAB_MANAGEMENT_TOKEN>"
}
}
}
}-
02
Save the file and restart Gemini CLI.
-
03
TokenLab Model Explorer is surfaced wherever your client lets you attach context. It is context to attach, not an action to run.
-
04
If it does not appear, check that TokenLab MCP Server is connected and that you are looking at its resources rather than its tools.
Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs
Set these first
TokenLab MCP Server will not start until these are set, so it never reaches Gemini CLI.
-
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 resource, other clients
Read from the server itself, by connecting to it and calling resources/list on 18 October 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.