How to integrate incident.io MCP with Claude Agent SDK

This guide walks you through connecting incident.io to the Claude Agent SDK 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 Claude Agent SDK 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.

Get started for freeGet a demo
incident.io logoincident.io
Api Key

incident.io is an incident management and response platform for modern teams. It helps streamline incident reporting, collaboration, and resolution.

112 Tools

Introduction

This guide walks you through connecting incident.io to the Claude Agent SDK 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 Claude Agent SDK 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.

Also integrate incident.io with

OpenAI Agents SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

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

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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.

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 step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A incident.io account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with incident.io functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  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 composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for incident.io
  const session = await composio.create(USER_ID, {
    toolkits: ['incident_io'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for incident.io
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to incident.io tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to incident.io
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

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

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with incident.io and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  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 composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['incident_io']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to incident.io tools via Composio.',
    maxTurns: 10,
  };

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

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with incident.io through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS

Supported Tools

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

Create Alert Attribute V2

Tool to create an alert attribute in incident.

Create Alert Route V2

Tool to create an alert route in incident.

Create Alert Source V2

Tool to create a new alert source in incident.

Create Catalog Entry V2

Tool to create a catalog entry in incident.

Create Catalog Entry V3

Tool to create a catalog entry in incident.

Create Catalog Type V3

Tool to create a new catalog type in incident.

Create Custom Field Option

Tool to create a new custom field option in incident.

Create Custom Field V2

Tool to create a custom field in incident.

Create Escalation V2

Tool to create an escalation in incident.

Create Incident Role

Tool to create a new incident role in incident.

Create Incident Role V2

Tool to create a new incident role in incident.

Create Incident Status

Tool to create a new incident status in incident.

Create Incident V1

Tool to create a new incident in incident.

Create Incident V2

Tool to create a new incident in incident.

Create Managed Resource V2

Tool to create a managed resource in incident.

Create Severity

Tool to create a new severity level in incident.

Delete Alert Attribute V2

Tool to delete an alert attribute from incident.

Delete Alert Route V2

Tool to delete an alert route from incident.

Delete Alert Source V2

Tool to delete an alert source from incident.

Delete Catalog Entry V2

Tool to delete a catalog entry from incident.

Delete Catalog Entry V3

Tool to archive a catalog entry from incident.

Delete Catalog Type V2

Tool to delete a catalog type from incident.

Delete Catalog Type V3

Tool to archive a catalog type and all its entries from incident.

Delete Custom Field

Tool to delete a custom field from incident.

Delete Custom Field Option

Tool to delete a custom field option in incident.

Delete Custom Field V2

Tool to delete a custom field from incident.

Delete Escalation Path V2

Tool to delete an escalation path from incident.

Delete Incident Role V2

Tool to delete an incident role by ID.

Delete Incident Role V1

Tool to delete an incident role by ID.

Delete Incident Status V1

Tool to delete an incident status by its ID.

Delete Schedule V2

Tool to delete a schedule from incident.

Delete Severity

Tool to delete a severity in incident.

Delete Workflow V2

Tool to delete a workflow from incident.

Edit Incident V2

Tool to edit an existing incident in incident.

Show Alert Attribute V2

Tool to retrieve a specific alert attribute by its ID from incident.

Show Alert Routes V2

Tool to retrieve a specific alert route configuration by its ID from incident.

Show Alert Source V2

Tool to retrieve a specific alert source by its ID from incident.

Show Entry Catalog V2

Tool to retrieve a specific catalog entry by ID from incident.

Get Catalog Entry V3

Tool to retrieve a specific catalog entry by ID from incident.

Get Catalog Type V2

Tool to retrieve a specific catalog type by ID from incident.

Get Catalog Type V3

Tool to retrieve a specific catalog type by ID from incident.

Get Custom Field Option

Tool to retrieve a specific custom field option by its ID.

Get Custom Field V1

Tool to retrieve details of a specific custom field by ID in incident.

Get Custom Field V2

Tool to retrieve details of a specific custom field by ID using the V2 API in incident.

Show Escalations V2

Tool to retrieve a specific escalation by ID from incident.

Get Incident Role

Tool to retrieve a specific incident role by ID.

Get Incident Role V2

Tool to retrieve a specific incident role by ID using V2 API.

Get Incident Status

Tool to retrieve details of a specific incident status by ID.

Get Incident Timestamp V2

Tool to retrieve a specific incident timestamp by ID using V2 API.

Get Incident Type

Tool 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 V2

Tool to retrieve a specific schedule by ID from incident.

Get Severity V1

Tool to retrieve a specific severity by ID from incident.

Get User V2

Tool to retrieve a specific user by ID from incident.

Get Workflow V2

Tool to retrieve a specific workflow by ID from incident.

List Actions V1

Tool to list actions from incidents.

List Actions V2

Tool to retrieve a list of actions from incident.

List Alert Attributes V2

Tool to list all available alert attributes.

List Alert Routes V2

Tool to list alert routes from incident.

List Alert Sources V2

Tool to list all configured alert sources in incident.

List Alerts V2

Tool to list alerts from incident.

List Catalog Entries V2

Tool to list entries from a catalog type in incident.

List Catalog Entries V3

Tool to list entries from a catalog type in incident.

List Catalog Resources V2

Tool to retrieve all available catalog resource types.

List Catalog Resources V3

Tool to retrieve all available catalog resource types from the V3 API.

List Catalog Types V2

Tool to retrieve all catalog types configured for an organization.

List Catalog Types V3

Tool to retrieve all catalog types configured for an organization using V3 API.

List Custom Field Options V1

Tool to list all options for a specific custom field in incident.

List Custom Fields V1

Tool to list all custom fields for an organization.

List Custom Fields V2

Tool to list all custom fields V2 for an organization.

List Escalation Paths V2

Tool to list escalation paths from incident.

List Escalations V2

Tool to list escalations from incident.

List Follow-ups V2

Tool to retrieve a list of follow-ups from incident.

Get API Key Identity

Tool to retrieve identity information for the current API key.

List Incident Alerts V2

Tool to list incident alerts from incident.

List Incident Attachments V1

Tool to list incident attachments from incident.

List Incident Relationships V1

Tool to list incident relationships for a given incident.

List Incident Roles V1

Tool to list all incident roles for an organization.

List Incident Roles V2

Tool to list all incident roles for an organization using V2 API.

List Incident Statuses V1

Tool to list all incident statuses configured for an organization.

List Incidents V1

Tool to list incidents from incident.

List Incidents V2

Tool to list incidents from incident.

List Incident Timestamps V2

Tool to list all incident timestamp configurations using V2 API.

List Incident Types V1

Tool to list all incident types for an organization.

List Incident Updates V2

Tool to list incident updates from incident.

List IP allowlists

Tool to retrieve the current IP allowlist configuration for incident.

List Schedule Entries V2

Tool to list schedule entries for a specific schedule in incident.

List Schedules V2

Tool to list schedules from incident.

List Severities V1

Tool to retrieve all incident severities configured for an organization.

List Status Pages V2

Tool to list status pages from incident.

List Users V2

Tool to list users in incident.

List Workflows V2

Tool to list workflows from incident.

Update Alert Attribute V2

Tool to update an alert attribute in incident.

Update Alert Source V2

Tool to update an existing alert source configuration in incident.

Bulk Update Catalog Entries V3

Tool to bulk update catalog entries in incident.

Update Catalog Entry V2

Tool to update an existing catalog entry in incident.

Update Catalog Entry V3

Tool to update an existing catalog entry in incident.

Update Catalog Type V2

Tool to update a catalog type in incident.

Update Catalog Type V3

Tool to update a catalog type in incident.

Update Custom Field Option V1

Tool to update a custom field option in incident.

Update Custom Fields V1

Tool to update an existing custom field configuration in incident.

Update Custom Field V2

Tool to update an existing custom field in incident.

Update Escalation Path V2

Tool to update an escalation path in incident.

Update Incident Role

Tool to update an existing incident role in incident.

Update Incident Role V2

Tool to update an existing incident role in incident.

Update Incident Status

Tool to update an existing incident status in incident.

Update Schedule V2

Tool to update an existing schedule in incident.

Update Catalog Type Schema V2

Tool to update the schema of a catalog type in incident.

Update Catalog Type Schema V3

Tool to update the schema of a catalog type in incident.

Update Severity

Tool to update a severity in incident.

Update Workflow V2

Tool to update an existing workflow in incident.

FRAMEWORKS

How to build incident.io MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use incident.io MCP with OpenAI Agents SDK

Claude Code logo

Claude Code

Use incident.io MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use incident.io MCP with Claude Cowork

Codex logo

Codex

Use incident.io MCP with Codex

OpenClaw logo

OpenClaw

Use incident.io MCP with OpenClaw

Hermes logo

Hermes

Use incident.io MCP with Hermes

CLI logo

CLI

Use incident.io MCP with CLI

Google ADK logo

Google ADK

Use incident.io MCP with Google ADK

LangChain logo

LangChain

Use incident.io MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use incident.io MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use incident.io MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use incident.io MCP with LlamaIndex

CrewAI logo

CrewAI

Use incident.io MCP with CrewAI

FAQ

Frequently asked questions

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.

Yes, you can. Claude Agent 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 incident.io tools.

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.

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.

Start with incident.io.It takes 30 seconds.

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

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies