How to integrate Bugsnag MCP with Mastra AI

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Bugsnag Logo
Mastra AI Logo
divider

Introduction

This guide walks you through connecting Bugsnag to Mastra AI 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 Mastra AI 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:
  • Set up your environment so Mastra, OpenAI, and Composio work together
  • Create a Tool Router session in Composio that exposes Bugsnag tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Bugsnag tool definitions and attach them as a toolset
  • Build a Mastra agent that can reason, call tools, and return structured results
  • Run an interactive CLI where you can chat with your Bugsnag agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

  • MCP Client: Built-in support for Model Context Protocol servers
  • Toolsets: Organize tools into logical groups
  • Step Callbacks: Monitor and debug agent execution
  • OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

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:
  • Node.js 18 or higher
  • A Composio account with an active API key
  • An OpenAI API key
  • Basic familiarity with TypeScript

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key.
  • You need credits or a connected billing setup to use the models.
  • Store the key somewhere safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Go to Settings and copy your API key.
  • This key lets your Mastra agent talk to Composio and reach Bugsnag through MCP.

Install dependencies

bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

  • @composio/core is the Composio SDK for creating MCP sessions
  • @mastra/core provides the Agent class
  • @mastra/mcp is Mastra's MCP client
  • @ai-sdk/openai is the model wrapper for OpenAI
  • dotenv loads environment variables from .env

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio
  • COMPOSIO_USER_ID tells Composio which user this session belongs to
  • OPENAI_API_KEY lets the Mastra agent call OpenAI models

Import libraries and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
What's happening:
  • dotenv/config auto loads your .env so process.env.* is available
  • openai gives you a Mastra compatible model wrapper
  • Agent is the Mastra agent that will call tools and produce answers
  • MCPClient connects Mastra to your Composio MCP server
  • Composio is used to create a Tool Router session

Create a Tool Router session for Bugsnag

typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["bugsnag"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Bugsnag MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "bugsnag" for Bugsnag access
  • session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
What's happening:
  • MCPClient takes an id for this client and a list of MCP servers
  • The headers property includes the x-api-key for authentication
  • getTools fetches the tool definitions exposed by the Bugsnag toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "bugsnag-mastra-agent",
    instructions: "You are an AI agent with Bugsnag tools via Composio.",
    model: "openai/gpt-5",
  });
What's happening:
  • Agent is the core Mastra agent
  • name is just an identifier for logging and debugging
  • instructions guide the agent to use tools instead of only answering in natural language
  • model uses openai("gpt-5") to configure the underlying LLM

Set up interactive chat interface

typescript
let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\n");

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        bugsnag: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • messages keeps the full conversation history in Mastra's expected format
  • agent.generate runs the agent with conversation history and Bugsnag toolsets
  • maxSteps limits how many tool calls the agent can take in a single run
  • onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

Here's the complete code to get you started with Bugsnag and Mastra AI:

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["bugsnag"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      bugsnag: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "bugsnag-mastra-agent",
    instructions: "You are an AI agent with Bugsnag tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { bugsnag: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Bugsnag through Composio's Tool Router. You can extend this further by:
  • Adding other toolkits like Gmail, Slack, or GitHub
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows

How to build Bugsnag MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Bugsnag MCP with OpenAI Agents SDK

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

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 Mastra AI?

Yes, you can. Mastra AI 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