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 VS Code Copilot 10 tools — connect in under 2 minutes

Name: BugSnag
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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.

GitHub Copilot Agent mode brings BugSnag data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the BugSnag MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using BugSnag

Ask Copilot: "Using BugSnag, help me..." — 10 tools available

Why Use VS Code Copilot with the BugSnag MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with BugSnag through the Model Context Protocol.

VS Code is used by over 70% of developers — adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

BugSnag + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the BugSnag MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

BugSnag MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect BugSnag to VS Code Copilot 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 VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot

Common issues when connecting BugSnag to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

BugSnag + VS Code Copilot FAQ

Common questions about integrating BugSnag MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.