How to integrate incident.io MCP with Mastra AI

GET STARTED FOR FREE
Framework Integration Gradient
incident.io Logo
Mastra AI Logo
divider

Introduction

This guide walks you through connecting incident.io to Mastra AI using the Composio tool router. By the end, you'll have a working incident.io agent that can create a new incident for database outage, list all active incidents from this week, assign on-call responder to latest incident through natural language commands.

This guide will help you understand how to give your Mastra AI agent real control over a incident.io account through Composio's incident.io 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 incident.io tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch incident.io 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 incident.io 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 incident.io MCP server, and what's possible with it?

The incident.io MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your incident.io account. It provides structured and secure access so your agent can perform incident.io operations on your behalf.

Supported Tools & Triggers

Tools
Create Alert Attribute V2Tool to create an alert attribute in incident.
Create Alert Route V2Tool to create an alert route in incident.
Create Alert Source V2Tool to create a new alert source in incident.
Create Catalog Entry V2Tool to create a catalog entry in incident.
Create Catalog Entry V3Tool to create a catalog entry in incident.
Create Catalog Type V3Tool to create a new catalog type in incident.
Create Custom Field OptionTool to create a new custom field option in incident.
Create Custom Field V2Tool to create a custom field in incident.
Create Escalation V2Tool to create an escalation in incident.
Create Incident RoleTool to create a new incident role in incident.
Create Incident Role V2Tool to create a new incident role in incident.
Create Incident StatusTool to create a new incident status in incident.
Create Incident V1Tool to create a new incident in incident.
Create Incident V2Tool to create a new incident in incident.
Create Managed Resource V2Tool to create a managed resource in incident.
Create SeverityTool to create a new severity level in incident.
Delete Alert Attribute V2Tool to delete an alert attribute from incident.
Delete Alert Route V2Tool to delete an alert route from incident.
Delete Alert Source V2Tool to delete an alert source from incident.
Delete Catalog Entry V2Tool to delete a catalog entry from incident.
Delete Catalog Entry V3Tool to archive a catalog entry from incident.
Delete Catalog Type V2Tool to delete a catalog type from incident.
Delete Catalog Type V3Tool to archive a catalog type and all its entries from incident.
Delete Custom FieldTool to delete a custom field from incident.
Delete Custom Field OptionTool to delete a custom field option in incident.
Delete Custom Field V2Tool to delete a custom field from incident.
Delete Escalation Path V2Tool to delete an escalation path from incident.
Delete Incident Role V2Tool to delete an incident role by ID.
Delete Incident Role V1Tool to delete an incident role by ID.
Delete Incident Status V1Tool to delete an incident status by its ID.
Delete Schedule V2Tool to delete a schedule from incident.
Delete SeverityTool to delete a severity in incident.
Delete Workflow V2Tool to delete a workflow from incident.
Edit Incident V2Tool to edit an existing incident in incident.
Show Alert Attribute V2Tool to retrieve a specific alert attribute by its ID from incident.
Show Alert Routes V2Tool to retrieve a specific alert route configuration by its ID from incident.
Show Alert Source V2Tool to retrieve a specific alert source by its ID from incident.
Show Entry Catalog V2Tool to retrieve a specific catalog entry by ID from incident.
Get Catalog Entry V3Tool to retrieve a specific catalog entry by ID from incident.
Get Catalog Type V2Tool to retrieve a specific catalog type by ID from incident.
Get Catalog Type V3Tool to retrieve a specific catalog type by ID from incident.
Get Custom Field OptionTool to retrieve a specific custom field option by its ID.
Get Custom Field V1Tool to retrieve details of a specific custom field by ID in incident.
Get Custom Field V2Tool to retrieve details of a specific custom field by ID using the V2 API in incident.
Show Escalations V2Tool to retrieve a specific escalation by ID from incident.
Get Incident RoleTool to retrieve a specific incident role by ID.
Get Incident Role V2Tool to retrieve a specific incident role by ID using V2 API.
Get Incident StatusTool to retrieve details of a specific incident status by ID.
Get Incident Timestamp V2Tool to retrieve a specific incident timestamp by ID using V2 API.
Get Incident TypeTool to retrieve detailed information about a specific incident type by ID.
Get Incident by ID (V1)Tool to retrieve a specific incident by ID.
Get Incident by ID (V2)Tool to retrieve a specific incident by ID using V2 API.
Show Schedules V2Tool to retrieve a specific schedule by ID from incident.
Get Severity V1Tool to retrieve a specific severity by ID from incident.
Get User V2Tool to retrieve a specific user by ID from incident.
Get Workflow V2Tool to retrieve a specific workflow by ID from incident.
List Actions V1Tool to list actions from incidents.
List Actions V2Tool to retrieve a list of actions from incident.
List Alert Attributes V2Tool to list all available alert attributes.
List Alert Routes V2Tool to list alert routes from incident.
List Alert Sources V2Tool to list all configured alert sources in incident.
List Alerts V2Tool to list alerts from incident.
List Catalog Entries V2Tool to list entries from a catalog type in incident.
List Catalog Entries V3Tool to list entries from a catalog type in incident.
List Catalog Resources V2Tool to retrieve all available catalog resource types.
List Catalog Resources V3Tool to retrieve all available catalog resource types from the V3 API.
List Catalog Types V2Tool to retrieve all catalog types configured for an organization.
List Catalog Types V3Tool to retrieve all catalog types configured for an organization using V3 API.
List Custom Field Options V1Tool to list all options for a specific custom field in incident.
List Custom Fields V1Tool to list all custom fields for an organization.
List Custom Fields V2Tool to list all custom fields V2 for an organization.
List Escalation Paths V2Tool to list escalation paths from incident.
List Escalations V2Tool to list escalations from incident.
List Follow-ups V2Tool to retrieve a list of follow-ups from incident.
Get API Key IdentityTool to retrieve identity information for the current API key.
List Incident Alerts V2Tool to list incident alerts from incident.
List Incident Attachments V1Tool to list incident attachments from incident.
List Incident Relationships V1Tool to list incident relationships for a given incident.
List Incident Roles V1Tool to list all incident roles for an organization.
List Incident Roles V2Tool to list all incident roles for an organization using V2 API.
List Incident Statuses V1Tool to list all incident statuses configured for an organization.
List Incidents V1Tool to list incidents from incident.
List Incidents V2Tool to list incidents from incident.
List Incident Timestamps V2Tool to list all incident timestamp configurations using V2 API.
List Incident Types V1Tool to list all incident types for an organization.
List Incident Updates V2Tool to list incident updates from incident.
List IP allowlistsTool to retrieve the current IP allowlist configuration for incident.
List Schedule Entries V2Tool to list schedule entries for a specific schedule in incident.
List Schedules V2Tool to list schedules from incident.
List Severities V1Tool to retrieve all incident severities configured for an organization.
List Status Pages V2Tool to list status pages from incident.
List Users V2Tool to list users in incident.
List Workflows V2Tool to list workflows from incident.
Update Alert Attribute V2Tool to update an alert attribute in incident.
Update Alert Source V2Tool to update an existing alert source configuration in incident.
Bulk Update Catalog Entries V3Tool to bulk update catalog entries in incident.
Update Catalog Entry V2Tool to update an existing catalog entry in incident.
Update Catalog Entry V3Tool to update an existing catalog entry in incident.
Update Catalog Type V2Tool to update a catalog type in incident.
Update Catalog Type V3Tool to update a catalog type in incident.
Update Custom Field Option V1Tool to update a custom field option in incident.
Update Custom Fields V1Tool to update an existing custom field configuration in incident.
Update Custom Field V2Tool to update an existing custom field in incident.
Update Escalation Path V2Tool to update an escalation path in incident.
Update Incident RoleTool to update an existing incident role in incident.
Update Incident Role V2Tool to update an existing incident role in incident.
Update Incident StatusTool to update an existing incident status in incident.
Update Schedule V2Tool to update an existing schedule in incident.
Update Catalog Type Schema V2Tool to update the schema of a catalog type in incident.
Update Catalog Type Schema V3Tool to update the schema of a catalog type in incident.
Update SeverityTool to update a severity in incident.
Update Workflow V2Tool to update an existing workflow in incident.

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 incident.io 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 incident.io

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

  const composioMCPUrl = session.mcp.url;
  console.log("incident.io MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "incident_io" for incident.io 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 incident.io toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "incident_io-mastra-agent",
    instructions: "You are an AI agent with incident.io 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: {
        incident_io: 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 incident.io 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 incident.io 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: ["incident_io"],
  });

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "incident_io-mastra-agent",
    instructions: "You are an AI agent with incident.io 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: { incident_io: 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 incident.io 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 incident.io MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use incident.io MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use incident.io MCP with Claude Agent SDK

Google ADK

Google ADK

Use incident.io MCP with Google ADK

LangChain

LangChain

Use incident.io MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use incident.io MCP with Vercel AI SDK

LlamaIndex

LlamaIndex

Use incident.io MCP with LlamaIndex

CrewAI

CrewAI

Use incident.io MCP with CrewAI

Claude Code

Claude Code

Use incident.io MCP with Claude Code

Codex

Codex

Use incident.io MCP with Codex

FAQ

What are the differences in Tool Router MCP and incident.io MCP?

With a standalone incident.io MCP server, the agents and LLMs can only access a fixed set of incident.io tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from incident.io 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 incident.io tools.

Can I manage the permissions and scopes for incident.io while using Tool Router?

Yes, absolutely. You can configure which incident.io 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 incident.io 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