MCP Debug Recorder

What this does

MCP Debug Recorder 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:

DEBUG_RECORDER_DB
LOG_LEVEL
FUZZY_THRESHOLD
DEBUG_RECORDER_REDACT_BEFORE_STORE
HOST
PORT
DEBUG_RECORDER_HTTP_TOKEN
DEBUG_RECORDER_ALLOWED_HOSTS
DEBUG_RECORDER_ALLOWED_ORIGINS
DEBUG_RECORDER_MAX_BODY_BYTES
DEBUG_RECORDER_REMOTE_HTTP

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

How do I install MCP Debug Recorder?

Run the Claude Code command in the install section to add MCP Debug Recorder 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 MCP Debug Recorder?

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 MCP Debug Recorder as well.

Does MCP Debug Recorder need an API key?

Yes. Before it can run, set these environment variables: DEBUG_RECORDER_DB, LOG_LEVEL, FUZZY_THRESHOLD, DEBUG_RECORDER_REDACT_BEFORE_STORE, HOST, PORT, DEBUG_RECORDER_HTTP_TOKEN, DEBUG_RECORDER_ALLOWED_HOSTS, DEBUG_RECORDER_ALLOWED_ORIGINS, DEBUG_RECORDER_MAX_BODY_BYTES, DEBUG_RECORDER_REMOTE_HTTP. They go in the env block of your MCP config.