npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@syncause/debug-mcp

v0.1.14

Published

Syncause Debug MCP Server

Readme

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:

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
    }
  }
}

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.