Cursor (MCP Server)

Access your DeepTracer data directly from Cursor. Ask "what errors happened today?" from your editor.

DeepTracer includes an MCP server that connects to Cursor. Once set up, you can ask Cursor about your production errors, search logs, and read AI investigation reports — all without leaving your editor.

Available Tools

When connected, Cursor gets access to 5 tools:

Tool	What it does
`get_errors`	List recent error groups with occurrence counts, severity, and resolution status. Supports filtering 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

Copy the MCP config

Go to your DeepTracer dashboard and navigate to Settings > Editor tab. Select the Cursor tab and copy the config JSON. It looks like this:

.cursor/mcp.json

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

Add it to Cursor

Open Cursor and go to Settings > MCP Servers. Paste the config JSON, or save it to .cursor/mcp.json in your project root.

Authorize

When Cursor connects for the first time, it will open a browser window asking you to authorize the connection. Sign in with your DeepTracer account and approve access.

That's it. Cursor now has access to your monitoring data.

Example Prompts

Once connected, try asking Cursor things like:

"Show me recent errors in production" — calls get_errors and returns a summary of your latest error groups.
"What's the stack trace for this error?" — pass a fingerprint and Cursor calls get_error_detail with full source-mapped traces.
"What happened with the last deployment?" — combines get_errors with get_health to give you a picture of how the deploy went.
"Search logs for payment failures" — calls search_logs with a search term to find matching log entries.
"Is my app healthy right now?" — calls get_health for the latest AI-generated health summary.
"What caused error abc123?" — calls get_investigation to get the root cause analysis and suggested fix.

All data is scoped to your organization. Cursor 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?

Claude Code Integration — Same tools, from the command line
Windsurf Integration — Connect Windsurf to DeepTracer
AI Investigations — Learn how the investigation reports work

On this page