Claude Code (MCP Server)

Access your DeepTracer data from Claude Code. Debug production errors without leaving the terminal.

DeepTracer includes an MCP server that connects to Claude Code. Once set up, you can ask about production errors, search logs, and read AI investigation reports — all from the command line.

Available Tools

When connected, Claude Code gets access to 5 tools:

Tool	What it does
`get_errors`	List recent error groups with occurrence counts, severity, and resolution status. Filter by environment, project, and service.
`get_error_detail`	Get full details for a specific error — stack trace (source-mapped when available), occurrence count, affected users, and recent occurrences.
`get_investigation`	Get the AI investigation report for an error — root cause analysis, evidence, blast radius, and suggested fix.
`search_logs`	Search through your application logs. Filter by environment, project, service, log level, time range, and search term.
`get_health`	Get the latest AI-generated health summary for your projects, including detected anomalies and metrics.

Setup

Run the setup command

Open your terminal and run:

claude mcp add --transport http deeptracer https://app.deeptracer.dev/mcp

That's the entire setup. Claude Code handles authentication automatically via OAuth.

Authorize

Claude Code will open a browser window asking you to sign in and authorize the connection. Approve access with your DeepTracer account.

This adds DeepTracer to your project-level MCP config. To make it available across all projects, add --scope user to the command.

Alternative: Manual config

You can also add it manually to your project's .mcp.json:

.mcp.json

{
  "mcpServers": {
    "deeptracer": {
      "type": "http",
      "url": "https://app.deeptracer.dev/mcp"
    }
  }
}

Or to your global config at ~/.claude/settings.json to make it available everywhere.

Example Usage

Once connected, you can ask Claude Code about your production data:

"What errors are happening in production?" — lists recent error groups with counts and status.
"Get the stack trace for error abc123" — shows full details including source-mapped stack trace.
"Search logs for 'timeout' in the last hour" — finds matching log entries with timestamps and metadata.
"Is my app healthy?" — returns the latest AI-generated health summary and anomalies.
"What caused the payment error? Show me the investigation." — returns the AI root cause analysis and suggested fix.

All data is scoped to your organization. Claude Code can only see projects you have access to in DeepTracer.

Managing Connections

You can see all connected editors and revoke access from Settings > Editor in your DeepTracer dashboard. Each connection shows when it was created and last used.

What's next?

Cursor Integration — Same tools, in Cursor's GUI
Windsurf Integration — Connect Windsurf to DeepTracer
AI Investigations — Learn how the investigation reports work

On this page