How to integrate Bugsnag MCP with Claude Code

Manage your Bugsnag directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: Via Composio Connect - Direct and easiest approach Via Composio SDK - Programmatic approach with more control

Bugsnag logoBugsnag
Api Key

Bugsnag is an error monitoring and stability management platform for software teams. It helps developers quickly detect, prioritize, and resolve application bugs for a smoother user experience.

60 Tools

Introduction

Manage your Bugsnag directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Bugsnag with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Bugsnag to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

What is the Bugsnag MCP server, and what's possible with it?

The Bugsnag MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Bugsnag account. It provides structured and secure access to your error monitoring environment, so your agent can perform actions like managing errors, configuring integrations, inviting collaborators, and customizing project event fields on your behalf.

  • Bulk error management and updates: Let your agent update or clear multiple errors across your projects to streamline incident response and maintenance.
  • Integration configuration and cleanup: Have your agent set up new third-party integrations or remove existing ones, ensuring your Bugsnag projects are always connected to the right tools.
  • User and collaborator management: Easily invite new collaborators to your organization or remove access for old members, keeping your team roster up to date.
  • Custom event field creation and deletion: Direct your agent to add or remove custom event fields for advanced filtering and analytics within your projects.
  • Project-level administration and cleanup: Instruct your agent to perform large-scale actions such as deleting all errors or even entire projects, giving you powerful administrative control when needed.

Connecting Bugsnag via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Bugsnag) for even more tool search precision. It's secure and reliable.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Bugsnag account
  • Basic knowledge of Python or TypeScript
2

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

3

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)
5

Install Composio library

npm install @composio/core dotenv

Install the Composio TypeScript library to create MCP sessions.

  • @composio/core provides the core Composio functionality
  • dotenv loads environment variables from your .env file
6

Generate Composio MCP URL

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['bugsnag'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http bugsnag-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Create a script to generate a Composio MCP URL for Bugsnag. This URL will be used to connect Claude Code to Bugsnag.

What's happening

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Bugsnag
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it
7

Run the script and copy the MCP URL

node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts

Run your TypeScript script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output
8

Add Bugsnag MCP to Claude Code

bash
claude mcp add --transport http bugsnag-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (bugsnag-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

9

Verify the installation

bash
claude mcp list

Check that your Bugsnag MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your bugsnag-composio entry in the list
  • This confirms that Claude Code can now access Bugsnag tools

If everything is wired up, you should see your bugsnag-composio entry listed:

Claude Code MCP list showing the toolkit MCP server
10

Authenticate Bugsnag

The first time you try to use Bugsnag tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Bugsnag
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Bugsnag authorization flow
  • Return to the terminal and start using Bugsnag through Claude Code

Once authenticated, you can ask Claude Code to perform Bugsnag operations in natural language. For example:

  • "Bulk update error statuses for project X"
  • "Invite new collaborator to my organization"
  • "Create a saved search for critical errors"

Complete Code

Here's the complete code to get you started with Bugsnag and Claude Code:

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['bugsnag'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http bugsnag-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Conclusion

You've successfully integrated Bugsnag with Claude Code using Composio's MCP server. Now you can interact with Bugsnag directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Bugsnag operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Bugsnag operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

TOOLS

Supported Tools

Every Bugsnag action and event your agent gets out of the box.

Add Collaborator to Teams

Tool to add a collaborator to a group of teams in a Bugsnag organization.

Add Collaborators to Team

Tool to add collaborators to a team in a Bugsnag organization.

Bulk Update Errors

Bulk update multiple errors in a Bugsnag project.

Configure Integration

Tool to configure a new integration for a Bugsnag project.

Confirm Project Event Data Deletion

Confirms a project event data deletion request in Bugsnag.

Invite Collaborator

Invites a new collaborator to a Bugsnag organization by email.

Create Custom Event Field

Creates a custom event field for a Bugsnag project, enabling filtering and pivoting on custom metadata.

Create Organization Project

Tool to create a new project in a Bugsnag organization.

Create Organization Team

Tool to create a new team in a Bugsnag organization.

Create Organization Data Deletion Request

Tool to create an event data deletion request for GDPR/CCPA compliance.

Create Organization Data Request

Tool to create an event data request for a Bugsnag organization (GDPR/CCPA compliance).

Create Project Event Data Deletion Request

Tool to create an event data deletion request for a specific project.

Create Project Event Data Request

Tool to create an event data request for a Bugsnag project.

Create Saved Search

Creates a saved search (filterset) for a Bugsnag project that persists filter and sort configurations.

Delete All Errors in a Project

Permanently deletes all errors and event data from a Bugsnag project.

Delete Collaborator

Removes a collaborator from a Bugsnag organization.

Delete a configured integration

Tool to delete a configured integration.

Delete Custom Event Field

Deletes a custom event field from a Bugsnag project.

Delete Organization

Permanently deletes a Bugsnag organization.

Delete Organization Team

Tool to delete a team from a Bugsnag organization.

Delete Project

Permanently deletes a Bugsnag project.

Delete Saved Search

Permanently deletes a saved search (filterset) from a Bugsnag project.

Get Configured Integration

Tool to retrieve details of a specific configured integration by its ID.

Get Organization By ID

Tool to view an organization by its ID.

Get Organization Collaborator Project Access Counts

Tool to view the project count of collaborators in an organization.

Get Organization Collaborator Projects

Tool to view projects a collaborator has access to in an organization.

Get Organization Event Data Request

Tool to check the status of an organization event data request.

Get Organization Team

Tool to show the details of a team in an organization.

Get Organization Data Deletion Status

Tool to check the status of an organization event data deletion request in Bugsnag.

Get Pivot Values on a Project

List pivot values for a project, showing how events are distributed across different values of a field.

Get Project Data Deletion Status

Tool to check the status of a project event data deletion request in Bugsnag.

Get Project Event Data Request

Tool to check the status of a project event data request.

Get Project Network Grouping Ruleset

Tool to retrieve a project's network grouping ruleset.

Get Saved Search

Retrieves the details of a specific saved search by its unique ID.

Get Saved Search Usage Summary

Retrieves usage statistics for a saved search, showing how it is being used across the project.

List Collaborator Access Details for Projects

Tool to list summary details of the projects a collaborator has access to.

List Collaborators

Tool to list collaborators in an organization.

List Collaborators on Project

Tool to list collaborators on a project.

List Configured Integrations for Project

Retrieves all configured integrations for a Bugsnag project.

List Errors on Project

List all errors in a Bugsnag project with optional filtering and sorting.

List Event Fields for Project

Lists all event fields available for filtering and pivoting in a Bugsnag project.

List Events for Error

Lists individual error event occurrences for a specific error group.

List Events on Project

List all error events for a Bugsnag project.

List Organizations

Tool to list organizations for the authenticated user.

List Organization Teams

Tool to list teams in an organization.

List Pivots for Project

Lists all pivot field definitions for a Bugsnag project.

List Project Feature Flags

List feature flags on a Bugsnag project for a specific release stage.

List Project Feature Flag Summaries

List feature flag summaries for a Bugsnag project with optional search filtering.

List Projects

Tool to list projects in an organization.

List Release Groups

Tool to list release groups for a project.

List Releases

List all releases (deployed versions) of a Bugsnag project.

List Saved Searches on Project

Lists all saved searches for a Bugsnag project.

List Supported Integrations

Tool to list all supported integrations.

List Trends for Project Buckets

Retrieves time-segmented event counts (trend buckets) for a Bugsnag project.

Regenerate Project API Key

Regenerates a Bugsnag project's notifier API key.

Show Collaborator Access Details for Project

Tool to show a collaborator's access details for a project.

Show Collaborator on Organization

Tool to show a collaborator in an organization.

Show Collaborator on Project

Tool to show a collaborator in a project.

Test Integration

Tool to test an integration configuration before deploying it.

Update Collaborator Permissions

Tool to update a collaborator's project access permissions.

FAQ

Frequently asked questions

With a standalone Bugsnag MCP server, the agents and LLMs can only access a fixed set of Bugsnag tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Bugsnag and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Bugsnag tools.

Yes, absolutely. You can configure which Bugsnag scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Bugsnag data and credentials are handled as safely as possible.

Start with Bugsnag.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Bugsnag tool your agent needs.Free to start.

Start building