open_tokenlab_model_explorer — TokenLab MCP Server MCP Tool
open_tokenlab_model_explorer
(open tokenlab model explorer) is one of 3 tools on the
TokenLab MCP Server
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call open_tokenlab_model_explorer from your client
- Claude Code TokenLab MCP Server open_tokenlab_model_explorer run in your project directory
- Claude Desktop TokenLab MCP Server open_tokenlab_model_explorer ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TokenLab MCP Server open_tokenlab_model_explorer ~/.cursor/mcp.json
- VS Code TokenLab MCP Server open_tokenlab_model_explorer .vscode/mcp.json
- Zed TokenLab MCP Server open_tokenlab_model_explorer ~/.config/zed/settings.json
- Windsurf TokenLab MCP Server open_tokenlab_model_explorer ~/.codeium/windsurf/mcp_config.json
- Cline TokenLab MCP Server open_tokenlab_model_explorer ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TokenLab MCP Server open_tokenlab_model_explorer ~/.gemini/settings.json
- Grok TokenLab MCP Server open_tokenlab_model_explorer .mcp.json (in your project root)
- LangChain TokenLab MCP Server open_tokenlab_model_explorer pip install langchain-mcp-adapters
Fastest route
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
Other tools on this server
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.