Can I check the stability trend for a project using the agent?

Yes! Use the `get_project_stats` tool with the Project ID. Your agent will fetch the error trends and statistics, allowing you to monitor health over time.

How do I list the top errors for my application?

Simply ask the agent to `list_errors` and provide the Project ID. It will retrieve the error groups from your BugSnag account, including messages and event counts.

Does the integration allow inspecting a specific error occurrence?

Yes. Use the `get_event` tool with the Event ID. It will retrieve the full details for that specific occurrence, which is helpful for deep debugging.

BugSnag MCP Server for Cursor 10 tools — connect in under 2 minutes

Name: BugSnag
Availability: InStock
Author: Vinkius

docs.cursor.com/context/model-context-protocol

Built by Vinkius GDPR 10 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install BugSnag and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

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

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About BugSnag MCP Server

Connect your BugSnag account to any AI agent and orchestrate your error monitoring, stability tracking, and incident response workflows through natural conversation.

Cursor's Agent mode turns BugSnag into an in-editor superpower. Ask Cursor to generate code using live data from BugSnag and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

What you can do

Organization Oversight — List all your organizations and projects to maintain visibility across your entire tech stack.
Error Management — List and inspect error groups for specific projects, including error classes, severity, and frequency.
Event Deep Dives — Retrieve individual error events and occurrence details to debug issues faster.
Team Coordination — Access your directory of collaborators and release stages to ensure everyone is aligned.
Stability Insights — Retrieve error trends and statistics to monitor the health of your applications over time.
Incident Response — Get detailed metadata for specific error or event IDs straight from your workspace.

The BugSnag MCP Server exposes 10 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect BugSnag to Cursor via MCP

Follow these steps to integrate the BugSnag MCP Server with Cursor.

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

Save the file

Cursor will automatically detect the new MCP server

Start using BugSnag

Open Agent mode in chat and ask: "Using BugSnag, help me...". 10 tools available

Why Use Cursor with the BugSnag MCP Server

Cursor AI Code Editor provides unique advantages when paired with BugSnag through the Model Context Protocol.

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

BugSnag + Cursor Use Cases

Practical scenarios where Cursor combined with the BugSnag MCP Server delivers measurable value.

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

BugSnag MCP Tools for Cursor (10)

These 10 tools become available when you connect BugSnag to Cursor via MCP:

get_error

Get details of a specific error group

get_event

Get details of a specific error event

get_project

Get details of a specific project

get_project_stats

Get error trends and statistics for a project

list_collaborators

List collaborators in an organization

list_errors

List error groups for a project

list_events

List individual error events for a project

list_organizations

List all organizations you have access to

list_projects

List all projects in an organization

list_release_stages

List release stages configured for a project

Example Prompts for BugSnag in Cursor

Ready-to-use prompts you can give your Cursor agent to start working with BugSnag immediately.

"List all my projects in BugSnag for organization org_123."

"Show the last 5 errors for the 'Web Dashboard' project."

"Get details for error group err_99283."

Troubleshooting BugSnag MCP Server with Cursor

Common issues when connecting BugSnag to Cursor through the Vinkius, and how to resolve them.

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

BugSnag + Cursor FAQ

Common questions about integrating BugSnag MCP Server with Cursor.

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.