Skip to main content
Book a demo

Connect SmartBear BugSnag to Cursor

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

Book a demo Cursor setup guide

Set up

Add SmartBear BugSnag to Cursor in four steps

Admins approve the server once. Everyone in Cursor 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 Cursor to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in Cursor, and admins can roll it out org-wide with Auto Sync plus a Cursor team rule. With direct tool listing turned on for your deployment, SmartBear BugSnag’s 19 tools show up in Cursor’s own tool list.

    Cursor 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 Cursor

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

Tools

19 SmartBear BugSnag tools in Cursor

Runlayer policy decides which of these Cursor 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 Cursor

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, Cursor 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 Cursor runs it, including calls to MCP servers.

  • Block output after it runs (available)

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

  • Redact output in place (not available)

    Cursor cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

In Cursor

  • Runlayer cannot tell Agents Window sessions apart from regular IDE sessions.
  • The Cursor CLI sends fewer session events than the IDE, but Runlayer’s allow and deny decisions still apply.

Frequently asked questions

Connect more

Find another combination