Skip to main content
Book a demo

Connect SmartBear BugSnag to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

Add SmartBear BugSnag to Cline CLI in four steps

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

    Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches SmartBear BugSnag’s 19 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Cline CLI 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 Cline CLI

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

Tools

19 SmartBear BugSnag tools in Cline CLI

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

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, Cline CLI 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 Cline CLI runs it.

  • Block output after it runs (not available)

    Cline CLI ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.

  • Redact output in place (not available)

    Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.

In Cline CLI

  • If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
  • This covers the Cline CLI, not the Cline extension for VS Code.

Frequently asked questions

Connect more

Find another combination