Debriefer
Clients

Claude Desktop

Connect Debriefer to Anthropic's Claude Desktop app.

Claude Desktop is the simplest way to use Debriefer — it runs the MCP server locally as a subprocess, so there's no hosting or networking to worry about.

Install

Add to ~/Library/Application Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%\Claude\claude_desktop_config.json · On Linux: ~/.config/Claude/claude_desktop_config.json
{  "mcpServers": {    "debriefer": {      "command": "npx",      "args": [        "@debriefer/mcp-server"      ],      "env": {        "DEBRIEFER_API_KEY": "sk_live_..."      }    }  }}
After saving, fully quit and relaunch Claude Desktop.

Verify it's connected

Open Claude Desktop's settings panel. Under Developer → MCP Servers, you should see debriefer listed with a green status indicator. If you don't, see Troubleshooting.

Try a prompt

Say this to Claude Desktop

List my most recent 5 interview runs and tell me which ones are still in progress.

Client-specific notes

  • Config path on Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Config path on Linux: ~/.config/Claude/claude_desktop_config.json
  • Server command: Claude Desktop launches npx @debriefer/mcp-server on startup. The first launch downloads the package, so give it a few seconds before tools appear.
  • Logs: Claude Desktop writes MCP server logs to ~/Library/Logs/Claude/mcp-server-debriefer.log on macOS. Useful when tool calls fail silently.
  • API key rotation: Update the key in your config file, then fully quit and relaunch Claude Desktop — a simple window-close won't reload env vars.

On this page