Grok TokenLab MCP Server Resource/TokenLab Model Explorer

Add TokenLab MCP Server to Grok

1. 01

   Open .mcp.json (in your project root) and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "tokenlab": {
      "type": "stdio",
      "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>"
      }
    }
  }
}

2. 02

   Save the file and restart Grok.

3. 03

   TokenLab Model Explorer is surfaced wherever your client lets you attach context. It is context to attach, not an action to run.

4. 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.

Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs

Same resource, other clients

• Claude Code
• Claude Desktop
• Cursor
• VS Code
• Zed
• Windsurf
• Cline
• Gemini CLI
• LangChain