Skip to main content
Book a demo

Connect SmartBear BugSnag to VS Code

Give VS Code governed access to SmartBear BugSnag’s 19 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo VS Code setup guide

Set up

Add SmartBear BugSnag to VS Code in four steps

Admins approve the server once. Everyone in VS Code then gets it through the same governed connection.

  1. 1

    Add SmartBear BugSnag to Runlayer

    SmartBear BugSnag isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect VS Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, SmartBear BugSnag’s 19 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).

    VS Code setup guide
  3. 3

    Sign in to SmartBear BugSnag

    Sign in the way SmartBear BugSnag requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use SmartBear BugSnag from VS Code

    SmartBear BugSnag’s approved tools appear in VS Code. Every call is checked against policy and recorded.

Tools

19 SmartBear BugSnag tools in VS Code

Runlayer policy decides which of these VS Code users can call.

  • Get build

    Get more details for a specific build by its ID

  • Get current project

    Retrieve the 'current' project on which tools should operate by default.

  • Get error

    Get full details on an error, including aggregated and summarized data across all events (occurrences) and details of the latest event (occurrence), such as breadcrumbs, metadata and the stacktrace.

  • Get event

    Get detailed information about a specific event

  • Get event details from dashboard URL

    Get detailed information about a specific event using its dashboard URL

  • Get events on an error

    Gets a list of events that have grouped into the specified error

  • Get network endpoint groupings

    Get the network endpoint grouping rules for a project

  • Get release

    Get more details for a specific release by its ID, including source control information and associated builds

See all 19 SmartBear BugSnag tools

Control

What Runlayer can see and stop in VS Code

Some controls apply to every client at the gateway. Others depend on what VS Code exposes to Runlayer.

  • Gateway policy (available)

    Every SmartBear BugSnag call from VS Code passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, VS Code as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before VS Code runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before VS Code’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.

Frequently asked questions

Connect more

Find another combination