How to integrate Bugsnag MCP with LlamaIndex

This guide walks you through connecting Bugsnag to LlamaIndex 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 your organization, create a saved search for critical errors through natural language commands. This guide will help you understand how to give your LlamaIndex 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.

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

This guide walks you through connecting Bugsnag to LlamaIndex 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 your organization, create a saved search for critical errors through natural language commands.

This guide will help you understand how to give your LlamaIndex 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.

Also integrate Bugsnag with

TL;DR

Here's what you'll learn:
  • Set your OpenAI and Composio API keys
  • Install LlamaIndex and Composio packages
  • Create a Composio Tool Router session for Bugsnag
  • Connect LlamaIndex to the Bugsnag MCP server
  • Build a Bugsnag-powered agent using LlamaIndex
  • Interact with Bugsnag through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

  • ReAct Agent: Reasoning and acting pattern for tool-using agents
  • MCP Tools: Native support for Model Context Protocol
  • Context Management: Maintain conversation context across interactions
  • Async Support: Built for async/await patterns

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.

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

What is Composio SDK?

Composio's Composio SDK 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 Composio SDK

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

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 you begin, make sure you have:
  • Python 3.8/Node 16 or higher installed
  • A Composio account with the API key
  • An OpenAI API key
  • A Bugsnag account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Bugsnag

OpenAI API key (OPENAI_API_KEY)
  • Go to the OpenAI dashboard
  • Create an API key if you don't have one
  • Assign it to OPENAI_API_KEY in .env
Composio API key and user ID
  • Log into the Composio dashboard
  • Copy your API key from Settings
    • Use this as COMPOSIO_API_KEY
  • Pick a stable user identifier (email or ID)
    • Use this as COMPOSIO_USER_ID
3

Installing dependencies

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

  • @composio/llamaindex: Composio's LlamaIndex integration
  • @llamaindex/openai: OpenAI LLM integration
  • @llamaindex/tools: MCP client for LlamaIndex
  • @llamaindex/workflow: Workflow framework for LlamaIndex
  • dotenv: Environment variable management
4

Set environment variables

bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

  • Authenticate with OpenAI's GPT-5 model
  • Connect to Composio's Tool Router
  • Identify your Composio user session for Bugsnag access
5

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called bugsnag_llamaindex_agent.ts and import the required modules:

Key imports:

  • dotenv.config loads .env at runtime
  • readline gives us a simple CLI chat loop
  • Composio is the main Composio SDK client
  • mcp connects to an MCP endpoint
  • createAgent builds a LlamaIndex agent
  • openai configures the LLM backend
6

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

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

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

7

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["bugsnag"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Bugsnag actions." ,
    llm,
    tools,
  });

  return agent;
}

What's happening here:

  • We create a Composio client using your API key and configure it with the LlamaIndex provider
  • We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, bugsnag)
  • The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
  • LlamaIndex will connect to this endpoint to dynamically discover and use the available Bugsnag tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
8

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

  • We're creating a direct terminal interface to chat with Bugsnag
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • The agent processes the request, selects appropriate Bugsnag tools, and returns a result
  • We extract the answer from the result data structure and display it to the user
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are streamed in a clear, readable format
9

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

What's happening here:

  • We're orchestrating the entire application flow
  • The agent gets built with proper error handling
  • Then we kick off the interactive chat loop so you can start talking to Bugsnag
10

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Bugsnag, then start asking questions.

Complete Code

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

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["bugsnag"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Bugsnag actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

Conclusion

You've successfully connected Bugsnag to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Bugsnag tools through an MCP endpoint
  • LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
  • The agent becomes more capable without increasing prompt size
  • Async Python provides clean, efficient execution of agent workflows
You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.
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. LlamaIndex 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