Stats Explorer MCP Server

What this does

Stats Explorer 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:

STATS_EXPLORER_ROOTS
STATS_EXPLORER_STREAM_MB
STATS_EXPLORER_WORKERS
STATS_EXPLORER_CACHE
STATS_EXPLORER_CACHE_DIR
STATS_EXPLORER_MAX_FILE_MB
STATS_EXPLORER_GUIDED
STATS_EXPLORER_CONFIRM_SELECTIONS
STATS_EXPLORER_CONFIRM_VIA
STATS_EXPLORER_HIDE_LINK
STATS_EXPLORER_JEV
STATS_EXPLORER_JEV_CHECKPOINTS
TYPESAFE_API_KEY
STATS_EXPLORER_APPROVAL_SECRET
STATS_EXPLORER_AUDIT_LOG

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

How do I install Stats Explorer?

Run the Claude Code command in the install section to add Stats Explorer 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 Stats Explorer?

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 Stats Explorer as well.

Does Stats Explorer need an API key?

Yes. Before it can run, set these environment variables: STATS_EXPLORER_ROOTS, STATS_EXPLORER_STREAM_MB, STATS_EXPLORER_WORKERS, STATS_EXPLORER_CACHE, STATS_EXPLORER_CACHE_DIR, STATS_EXPLORER_MAX_FILE_MB, STATS_EXPLORER_GUIDED, STATS_EXPLORER_CONFIRM_SELECTIONS, STATS_EXPLORER_CONFIRM_VIA, STATS_EXPLORER_HIDE_LINK, STATS_EXPLORER_JEV, STATS_EXPLORER_JEV_CHECKPOINTS, TYPESAFE_API_KEY, STATS_EXPLORER_APPROVAL_SECRET, STATS_EXPLORER_AUDIT_LOG. They go in the env block of your MCP config.