How to integrate Bugsnag MCP with OpenAI Agents SDK

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Bugsnag Logo
open-ai-agents-sdk Logo
divider

Introduction

This guide walks you through connecting Bugsnag to the OpenAI Agents SDK using the Composio tool router. By the end, you'll have a working Bugsnag agent that can bulk update error statuses for project x, invite new collaborator to my organization, create a saved search for critical errors, delete all errors in the staging project through natural language commands.

This guide will help you understand how to give your OpenAI Agents SDK agent real control over a Bugsnag account through Composio's Bugsnag MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Bugsnag
  • Configure an AI agent that can use Bugsnag as a tool
  • Run a live chat session where you can ask the agent to perform Bugsnag operations

What is open-ai-agents-sdk?

The OpenAI Agents SDK is a lightweight framework for building AI agents that can use tools and maintain conversation state. It provides a simple interface for creating agents with hosted MCP tool support.

Key features include:

  • Hosted MCP Tools: Connect to external services through hosted MCP endpoints
  • SQLite Sessions: Persist conversation history across interactions
  • Simple API: Clean interface with Agent, Runner, and tool configuration
  • Streaming Support: Real-time response streaming for interactive applications

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.

Supported Tools & Triggers

Tools
Bulk Update ErrorsTool to bulk update multiple errors in a project.
Configure IntegrationTool to configure a new integration for a bugsnag project.
Invite CollaboratorTool to invite a collaborator to an organization.
Create Custom Event FieldTool to create a custom event field for a project.
Create Saved SearchTool to create a new saved search for a project.
Delete All Errors in a ProjectTool to delete all errors in a project.
Delete CollaboratorTool to remove a collaborator from an organization.
Delete a configured integrationTool to delete a configured integration.
Delete Event FieldTool to delete a custom event field.
Delete ProjectTool to delete a project.
Delete Saved SearchTool to delete a saved search.
Get Saved SearchTool to retrieve a saved search by id.
Get Saved Search Usage SummaryTool to get usage summary for a saved search.
List Collaborator Access Details for ProjectsTool to list summary details of the projects a collaborator has access to.
List CollaboratorsTool to list collaborators in an organization.
List Collaborators on ProjectTool to list collaborators on a project.
List Configured Integrations for ProjectTool to list configured integrations for a project.
List Errors on ProjectTool to list all errors in a project.
List Event Fields for ProjectTool to list event fields for a project.
List Events on ProjectTool to list events for a project.
List OrganizationsTool to list organizations for the authenticated user.
List Pivots for ProjectTool to list pivots for a project.
List ProjectsTool to list projects in an organization.
List Release GroupsTool to list release groups for a project.
List ReleasesTool to list releases for a project.
List Saved Searches on ProjectTool to list saved searches for a project.
List Supported IntegrationsTool to list all supported integrations.
List Trends for Project BucketsTool to list trend buckets for a project.
Regenerate Project API KeyTool to regenerate a project's api key.
Show Collaborator Access Details for ProjectTool to show a collaborator's access details for a project.
Show Collaborator on OrganizationTool to show a collaborator in an organization.
Show Collaborator on ProjectTool to show a collaborator in a project.
Update Collaborator PermissionsTool to update a collaborator's project access permissions.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router 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

Prerequisites

Before starting, make sure you have:
  • Composio API Key and OpenAI API Key
  • Primary know-how of OpenAI Agents SDK
  • A live Bugsnag project
  • Some knowledge of Python or Typescript

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key

Install dependencies

pip install composio_openai_agents openai-agents python-dotenv

Install the Composio SDK and the OpenAI Agents SDK.

Set up environment variables

bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com

Create a .env file and add your OpenAI and Composio API keys.

Import dependencies

import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession
What's happening:
  • You're importing all necessary libraries.
  • The Composio and OpenAIAgentsProvider classes are imported to connect your OpenAI agent to Composio tools like Bugsnag.

Set up the Composio instance

load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())
What's happening:
  • load_dotenv() loads your .env file so OPENAI_API_KEY and COMPOSIO_API_KEY are available as environment variables.
  • Creating a Composio instance using the API Key and OpenAIAgentsProvider class.

Create a Tool Router session

# Create a Bugsnag Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["bugsnag"]
)

mcp_url = session.mcp.url

What is happening:

  • You give the Tool Router the user id and the toolkits you want available. Here, it is only bugsnag.
  • The router checks the user's Bugsnag connection and prepares the MCP endpoint.
  • The returned session.mcp.url is the MCP URL that your agent will use to access Bugsnag.
  • This approach keeps things lightweight and lets the agent request Bugsnag tools only when needed during the conversation.

Configure the agent

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Bugsnag. "
        "Help users perform Bugsnag operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)
What's happening:
  • We're creating an Agent instance with a name, model (gpt-5), and clear instructions about its purpose.
  • The agent's instructions tell it that it can access Bugsnag and help with queries, inserts, updates, authentication, and fetching database information.
  • The tools array includes a HostedMCPTool that connects to the MCP server URL we created earlier.
  • The headers dict includes the Composio API key for secure authentication with the MCP server.
  • require_approval: 'never' means the agent can execute Bugsnag operations without asking for permission each time, making interactions smoother.

Start chat loop and handle conversation

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
What's happening:
  • The program prints a session URL that you visit to authorize Bugsnag.
  • After authorization, the chat begins.
  • Each message you type is processed by the agent using Runner.run().
  • The responses are printed to the console, and conversations are saved locally using SQLite.
  • Typing exit, quit, or q cleanly ends the chat.

Complete Code

Here's the complete code to get you started with Bugsnag and open-ai-agents-sdk:

import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession

load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())

# Create Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["bugsnag"]
)
mcp_url = session.mcp.url

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Bugsnag. "
        "Help users perform Bugsnag operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())

Conclusion

This was a starter code for integrating Bugsnag MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Bugsnag.

Key features:

  • Hosted MCP tool integration through Composio's Tool Router
  • SQLite session persistence for conversation history
  • Simple async chat loop for interactive testing
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Bugsnag MCP Agent with another framework

Claude Agent SDK

Claude Agent SDK

Use Bugsnag MCP with Claude Agent SDK

Google ADK

Google ADK

Use Bugsnag MCP with Google ADK

LangChain

LangChain

Use Bugsnag MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Bugsnag MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Bugsnag MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Bugsnag MCP with LlamaIndex

CrewAI

CrewAI

Use Bugsnag MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Bugsnag MCP?

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.

Can I use Tool Router MCP with OpenAI Agents SDK?

Yes, you can. OpenAI Agents SDK 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.

Can I manage the permissions and scopes for Bugsnag while using Tool Router?

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.

How safe is my data with Composio Tool Router?

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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a callā†—Get started for free