Connect SmartBear BugSnag to Claude Code
Give Claude Code governed access to SmartBear BugSnag’s 19 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add SmartBear BugSnag to Claude Code in four steps
Admins approve the server once. Everyone in Claude Code then gets it through the same governed connection.
- 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
Connect Claude Code to Runlayer
Runlayer’s CLI installs the Runlayer Plugin natively in Claude Code, and an Anthropic org install also reaches Claude Code. With direct tool listing turned on for your deployment, SmartBear BugSnag’s 19 tools show up in Claude Code’s own tool list (supported Claude Code versions).
Claude Code setup guide - 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
Use SmartBear BugSnag from Claude Code
SmartBear BugSnag’s approved tools appear in Claude Code. Every call is checked against policy and recorded.
Tools
19 SmartBear BugSnag tools in Claude Code
Runlayer policy decides which of these Claude 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
Control
What Runlayer can see and stop in Claude Code
Some controls apply to every client at the gateway. Others depend on what Claude Code exposes to Runlayer.
Gateway policy (available)
Every SmartBear BugSnag call from Claude Code passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Claude 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.
Anthropic inference hooks (available)
With Claude Enterprise, Anthropic sends each governed Claude Code prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).
OTLP telemetry (available)
Claude Code can export OpenTelemetry logs to Runlayer for observe-only session reconstruction.
Stop a call before it runs (available)
Runlayer can deny a tool call before Claude Code runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Claude Code’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a tool’s output in Claude Code and pass the rest through.
In Claude Code
- When a tool fails, Runlayer records the error but cannot hide it.
Frequently asked questions
Connect more
