Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
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.
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.
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" }
}
}
}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@latestAPI_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@latestEdit ~/.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: agent-debugger
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@latestEnv not applied → many clients require restarting after config changes.
Your API_KEY is sensitive. Avoid committing MCP config files to Git.
Prefer project-level configs only when you need per-repo isolation.
This server cannot be deployed
Open-source agent that observes and fixes your application. Query logs, traces, metrics, incidents.
Codebase intelligence for AI agents — dead code, blast radius, ownership.
Shared debugging memory for AI coding agents
Give AI coding agents access to your Vynix visual feedback, bug reports, and AI diagnosis.
