Which integrations are available for this server?

Integrates with Windsurf (Codeium's IDE) to capture and query runtime debugging data via MCP. Integrates with OpenAI Codex CLI to provide runtime facts for debugging via MCP.

How do I use syncause-debug-mcp?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@syncause-debug-mcp get stack trace from the last error" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

syncause-debug-mcp

by Syncause

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Syncause Debug MCP Server

Without Syncause, coding agents often guess and only fix symptoms, so you may need to prompt the agent multiple times to fix the root cause.

With Syncause, agents can fix the root cause in one go. Syncause captures runtime facts (stack traces, logs, request/response, function arguments, and key variable values) and makes it queryable by AI agents via MCP—so the agent debugs with evidence instead of guessing.

Use it with:

Syncause IDE Extension — capture runtime data in your IDE, then query it via MCP.
Syncause Debugger Skill — a prompt/workflow layer that calls this MCP server.

Installation

NOTE

API Key Recommended: Get a free API key at syn-cause.com/dashboard for higher rate limits.

Common MCP Configuration works in most of the tools:

{
  "mcpServers": {
    "syncause-debug-mcp": {
      "command": "npx",
      "args": ["-y", "@syncause/debug-mcp@latest"],
      "env": { "API_KEY": "YOUR_API_KEY" }
    }
  }
}

Configure in your client

Edit .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "syncause-debug-mcp": {
      "command": "npx",
      "args": ["-y", "@syncause/debug-mcp@latest"],
      "env": { "API_KEY": "YOUR_API_KEY" }
    }
  }
}

Edit .vscode/settings.json:

{
  "mcp.servers": {
    "syncause-debug-mcp": {
      "command": "npx",
      "args": ["-y", "@syncause/debug-mcp@latest"],
      "env": { "API_KEY": "YOUR_API_KEY" }
    }
  }
}

Edit ~/.gemini/antigravity/mcp_config.json (Global):

{
  "mcp.servers": {
    "syncause-debug-mcp": {
      "command": "npx",
      "args": ["-y", "@syncause/debug-mcp@latest"],
      "env": { "API_KEY": "YOUR_API_KEY" }
    }
  }
}

Run this command (local stdio server):

API_KEY=YOUR_API_KEY claude mcp add syncause-debug-mcp -- npx -y @syncause/debug-mcp@latest

API_KEY=YOUR_API_KEY codex mcp add syncause-debug-mcp --command "npx -y @syncause/debug-mcp@latest"

API_KEY=YOUR_API_KEY gemini mcp add syncause-debug-mcp -- npx -y @syncause/debug-mcp@latest

Edit ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "syncause-debug-mcp": {
      "command": "npx",
      "args": ["-y", "@syncause/debug-mcp@latest"],
      "env": { "API_KEY": "YOUR_API_KEY" }
    }
  }
}

Edit ~/.config/goose/config.yaml:

extensions:
  syncause-debug-mcp:
    type: stdio
    name: Syncause Debug MCP
    enabled: true
    timeout: 300
    cmd: npx
    args: ["-y", "@syncause/debug-mcp@latest"]
    envs:
      API_KEY: "YOUR_API_KEY"

Add this to your Opencode config:

{
  "mcp": {
    "syncause-debug-mcp": {
      "type": "local",
      "command": ["npx", "-y", "@syncause/debug-mcp@latest"],
      "env": { "API_KEY": "YOUR_API_KEY" },
      "enabled": true
    }
  }
}

Related MCP server: Log Diagnosis MCP Server

Troubleshooting

npx: command not found → install Node.js (or ensure your shell can find it).
Server won’t start in your client → try running the MCP server directly in a terminal first:
```
npx -y @syncause/debug-mcp@latest
```
Env not applied → many clients require restarting after config changes.

Security Notes

Your API_KEY is sensitive. Avoid committing MCP config files to Git.
Prefer project-level configs only when you need per-repo isolation.

Available Tools

6 tools

diff_trace_executionB

Compare the execution paths and data differences between two requests (usually one successful and one failed) to identify the root cause of bugs.

Inputs: projectId (required), baseTraceId (required), compareTraceId.

get_project_listA

List all projects that have already been initialized. This is the preferred way to discover available 'projectId's and their corresponding paths without re-initializing them.

Inputs: no named parameters.

get_trace_insightA

Get a complete lifecycle report for a single request, including call tree skeleton, key SQL summaries, and exception logs.

Inputs: traceId (required), projectId (required).

inspect_method_snapshotB

Deep dive into a specific method for a given request, returning precise input/output parameters, local variables, and logs generated within its scope.

Inputs: traceId (required), className (required), projectId (required), methodName (required), +1 more.

search_debug_tracesB

Entry point for troubleshooting. Search for relevant error logs, slow queries, or specific business ID execution traces based on user questions or error descriptions.

Inputs: query (required), projectId (required), limit, since.

setup_projectA

Initialize or retrieve a specific project's configuration by its path. Use this when you have a local project path and need its 'projectId'. If you want to see already configured projects, use 'get_project_list' first.

Inputs: projectPath (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

Deploy Server

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

TDQS

A3.7/5.0

Scored 2026-11-04 19:00 across 6 tools

Disambiguation4/5

Each tool targets a distinct level of the tracing workflow: discovery (search_debug_traces), request-level report (get_trace_insight), method-level drill-down (inspect_method_snapshot), comparison (diff_trace_execution), and project config (setup_project/get_project_list). The only mild overlap is between search_debug_traces and get_trace_insight, since both surface logs/errors, but the descriptions clarify search is the entry point and insight is a full lifecycle report.

Naming Consistency4/5

All names follow a snake_case verb_noun pattern (get_trace_insight, search_debug_traces, inspect_method_snapshot, diff_trace_execution, setup_project, get_project_list). Minor deviation: 'diff' and 'setup' are less standard verbs than get/search/inspect, and project tools split verbs (get vs setup) for related concepts, but overall the convention is predictable.

Tool Count5/5

Six tools is well-scoped for a trace-debugging server: two for project setup/discovery and four covering the search-to-diagnosis-to-comparison flow. No tool appears redundant or filler.

Completeness4/5

The core lifecycle (discover project, search traces, inspect request and method detail, diff two requests) is fully covered. Minor gaps exist around project config lifecycle (no removal/reset of an initialized project) and no way to list or browse recent traces without a search query, but agents can work around these.

Maintenance

ActivityNo data

ResponsivenessOutdated data

Resources

Related MCP Connectors

BugTape
ai.bugtape
Production bugs with replay, network, console and stack, ranked for your coding agent to fix.
Monitoring Observability Developer Tools
1
https://app.bugtape.ai/mcp
Superlog
sh.superlog
Open-source agent that observes and fixes your application. Query logs, traces, metrics, incidents.
Monitoring Observability
21,039
https://api.superlog.sh/mcp
Mapnostics
io.github.ffteema
Codebase intelligence for AI agents — dead code, blast radius, ownership.
Code Analysis Developer Tools
1
https://www.mapnostics.com/api/mcp
RunheedA
com.runheed
Production errors your coding agent can read: search, stack traces, context, trends, resolve.
Monitoring Observability Developer Tools
91
https://runheed.com/api/mcp

Related MCP Servers

agent-debugger
Observability Monitoring Autonomous Agents
UnCooe
A
license
Not graded
quality
D
maintenance
Enables AI agents to investigate backend incidents by executing runbooks that gather evidence from observability and storage systems.
Updated 5 months ago (2026-06-21 14:25 UTC)
7 npm
9
MIT
Log Diagnosis MCP Server
Monitoring Observability
suxiao1228
A
license
Not graded
quality
D
maintenance
Enables AI to automatically diagnose bugs by querying logs, tracing call chains, and analyzing code across multiple log platforms like Elasticsearch and Loki.
Updated 7 months ago (2026-04-02 11:02 UTC)
MIT
DevContext
Observability Monitoring
sid-stack001
A
license
Not graded
quality
C
maintenance
Enables coding agents to access live runtime observability data such as logs, deploys, and health metrics for evidence-based incident triage.
Updated 3 months ago (2026-08-24 18:14 UTC)
1
MIT
Production Monitoring MCP
Observability Monitoring Developer Tools
kowshik3383
A
license
A
quality
B
maintenance
Connects AI agents to live observability stacks including Sentry, GitHub, Vercel, Better Stack, and Cloudflare, enabling end-to-end incident investigation, deployment correlation, root cause analysis, and regression triage.
Updated 2 months ago (2026-09-13 05:56 UTC)
14
MIT

Syncause Debug MCP Server

Installation

Configure in your client

Troubleshooting

Security Notes

Available Tools

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

agent-debugger

Log Diagnosis MCP Server

DevContext

Production Monitoring MCP