TokenLab MCP Server

What this does

TokenLab MCP Server exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

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

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install TokenLab MCP Server?

Run the Claude Code command in the install section to add TokenLab MCP Server to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with TokenLab MCP Server?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to TokenLab MCP Server as well.

Does TokenLab MCP Server need an API key?

Yes. Before it can run, set these environment variables: 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. They go in the env block of your MCP config.