How to Use the BugSnag MCP in Windsurf

Q: How does Windsurf use BugSnag to auto-fix errors?

Cascade chains geterror with its codebase search to find the exact file causing the crash. It then writes the patch and runs your local tests to verify the fix.

Q: Can I filter BugSnag errors by release stage in Windsurf?

Yes, Cascade uses listreleasestages to filter out staging noise. This lets you focus only on issues currently affecting production users.

Q: How do I configure this BugSnag MCP Server in Windsurf?

Open your /.codeium/windsurf/mcpconfig.json configuration file and add the server under the mcpServers key. Cascade will automatically discover the tools once you hit refresh.

Let Cascade hunt down and debug BugSnag production crashes in Windsurf before you even open a browser tab.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect BugSnag MCP to Windsurf

Create your Vinkius account to connect BugSnag to Windsurf and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup BugSnag with Windsurf

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Auto-diagnose Windsurf crashes with BugSnag

Cascade uses `get_error` and `get_event` to pull BugSnag crash details straight into Windsurf without you copy-pasting stack traces. You do not have to manually dig through log files anymore. Cascade reads the error context, matches it to your local workspace files, and immediately drafts a fix.

Track project health trends inside your IDE

This MCP Server lets your agent use `get_project_stats` and `list_release_stages` to evaluate if a recent deploy caused a regression. Cascade compares these stats against your active git branch. If errors spike in a specific stage, it alerts you before you push more code.

Map team ownership to active bugs

The agent runs `list_collaborators` and `list_errors` to map team ownership to active BugSnag bugs directly in your Windsurf workspace. It speeds up triage by assigning the fix draft to the right person. No more endless Slack threads trying to find out who owns a broken endpoint.

Setup guide

Set up BugSnag MCP in Windsurf

Prerequisites

Windsurf IDE installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Click the Cascade assistant icon in the sidebar, then click the hammer icon (🔨) at the top of the panel. Select "Configure" to open ~/.codeium/windsurf/mcp_config.json.
2

Add the BugSnag MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Refresh MCPs

Go back to the hammer icon (🔨) in Cascade and click "Refresh". Windsurf will detect the new server. No full restart is needed — the connection is hot-reloaded.
4

Verify in Cascade

Start a new Cascade conversation and ask something like "Show my BugSnag payment history." If connected, Cascade will call the BugSnag tools directly. You will see a green dot next to the server name in the MCP panel.

mcp_config.json

{
  "mcpServers": {
    "bugsnag-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by BugSnag. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect BugSnag now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about BugSnag MCP in Windsurf

Cascade chains `get_error` with its codebase search to find the exact file causing the crash. It then writes the patch and runs your local tests to verify the fix.

Yes, Cascade uses `list_release_stages` to filter out staging noise. This lets you focus only on issues currently affecting production users.

Open your `~/.codeium/windsurf/mcp_config.json` configuration file and add the server under the mcpServers key. Cascade will automatically discover the tools once you hit refresh.

No, you can configure Cascade to run these read-only tools autonomously. It will fetch the crash data and present the final diagnosis in one go.

Your crash logs and stack traces never leave the secure Vinkius sandbox. We only transmit the specific JSON error payloads required to diagnose the active bug.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript