Connect SmartBear BugSnag to Warp
Give Warp 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 Warp in four steps
Admins approve the server once. Everyone in Warp 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 Warp to Runlayer
Users add the Runlayer Plugin to Warp by following Runlayer’s setup guide. Warp reaches SmartBear BugSnag’s 19 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Warp 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 Warp
SmartBear BugSnag’s approved tools appear in Warp. Every call is checked against policy and recorded.
Tools
19 SmartBear BugSnag tools in Warp
Runlayer policy decides which of these Warp 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 Warp
Some controls apply to every client at the gateway. Others depend on what Warp exposes to Runlayer.
Gateway policy (available)
Every SmartBear BugSnag call from Warp passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Warp as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Warp yet, so control happens at the gateway.
Frequently asked questions
Connect more