Skip to content

VS Code TokenLab MCP Server Resource/TokenLab Model Explorer

How to: VS Code TokenLab MCP Server TokenLab Model Explorer

client:VS Code transport:stdio resource:TokenLab Model Explorer

Add TokenLab MCP Server to VS Code

  1. 01

    Open .vscode/mcp.json and merge this in. Keep any servers already there.

{
  "inputs": [
    {
      "type": "promptString",
      "id": "tokenlab-api-base",
      "description": "TOKENLAB_API_BASE",
      "password": true
    },
    {
      "type": "promptString",
      "id": "tokenlab-api-key",
      "description": "TOKENLAB_API_KEY",
      "password": true
    },
    {
      "type": "promptString",
      "id": "tokenlab-request-timeout-ms",
      "description": "TOKENLAB_REQUEST_TIMEOUT_MS",
      "password": true
    },
    {
      "type": "promptString",
      "id": "tokenlab-mcp-tool-profile",
      "description": "TOKENLAB_MCP_TOOL_PROFILE",
      "password": true
    },
    {
      "type": "promptString",
      "id": "tokenlab-mcp-schema-mode",
      "description": "TOKENLAB_MCP_SCHEMA_MODE",
      "password": true
    },
    {
      "type": "promptString",
      "id": "tokenlab-mcp-max-file-bytes",
      "description": "TOKENLAB_MCP_MAX_FILE_BYTES",
      "password": true
    },
    {
      "type": "promptString",
      "id": "tokenlab-mcp-inline-bytes",
      "description": "TOKENLAB_MCP_INLINE_BYTES",
      "password": true
    },
    {
      "type": "promptString",
      "id": "tokenlab-artifact-dir",
      "description": "TOKENLAB_ARTIFACT_DIR",
      "password": true
    },
    {
      "type": "promptString",
      "id": "tokenlab-management-token",
      "description": "TOKENLAB_MANAGEMENT_TOKEN",
      "password": true
    }
  ],
  "servers": {
    "tokenlab": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@tokenlabai/mcp-server"
      ],
      "env": {
        "TOKENLAB_API_BASE": "${input:tokenlab-api-base}",
        "TOKENLAB_API_KEY": "${input:tokenlab-api-key}",
        "TOKENLAB_REQUEST_TIMEOUT_MS": "${input:tokenlab-request-timeout-ms}",
        "TOKENLAB_MCP_TOOL_PROFILE": "${input:tokenlab-mcp-tool-profile}",
        "TOKENLAB_MCP_SCHEMA_MODE": "${input:tokenlab-mcp-schema-mode}",
        "TOKENLAB_MCP_MAX_FILE_BYTES": "${input:tokenlab-mcp-max-file-bytes}",
        "TOKENLAB_MCP_INLINE_BYTES": "${input:tokenlab-mcp-inline-bytes}",
        "TOKENLAB_ARTIFACT_DIR": "${input:tokenlab-artifact-dir}",
        "TOKENLAB_MANAGEMENT_TOKEN": "${input:tokenlab-management-token}"
      }
    }
  }
}
  1. 02

    Save the file and restart VS Code.

  2. 03

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

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

VS Code prompts for each input the first time the server starts, so no secret is written to the file. VS Code docs

Set these first

TokenLab MCP Server will not start until these are set, so it never reaches VS Code.

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