incident.io with Pydantic AI

How to integrate incident.io MCP with Pydantic AI

Introduction TL;DR What is Pydantic AI What is the incident.io MCP server Supported Tools & Triggers Creating MCP Server - Stand-alone vs Tool Router Step-by-step Guide Complete Code Conclusion How to build incident.io MCP Agent with another framework Explore Other Toolkits FAQ

Connect incident.io without Auth hassles

We manage OAuth, API Key, token refresh, and scopes, you just build.

Try for Free

Introduction

This guide walks you through connecting incident.io to Pydantic 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 Pydantic 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:

How to set up your Composio API key and User ID
How to create a Composio Tool Router session for incident.io
How to attach an MCP Server to a Pydantic AI agent
How to stream responses and maintain chat history
How to build a simple REPL-style chat interface to test your incident.io workflows

What is Pydantic AI?

Pydantic AI is a Python framework for building AI agents with strong typing and validation. It leverages Pydantic's data validation capabilities to create robust, type-safe AI applications.

Key features include:

Type Safety: Built on Pydantic for automatic data validation
MCP Support: Native support for Model Context Protocol servers
Streaming: Built-in support for streaming responses
Async First: Designed for async/await patterns

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:

Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:

Python 3.9 or higher
A Composio account with an active API key
Basic familiarity with Python and async programming

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

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.

Install dependencies

bash

pip install composio pydantic-ai python-dotenv

Install the required libraries.

What's happening:

composio connects your agent to external SaaS tools like incident.io
pydantic-ai lets you create structured AI agents with tool support
python-dotenv loads your environment variables securely from a .env file

Set up environment variables

bash

COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key

Create a .env file in your project root.

What's happening:

COMPOSIO_API_KEY authenticates your agent to Composio's API
USER_ID associates your session with your account for secure tool access
OPENAI_API_KEY to access OpenAI LLMs

Import dependencies

python

import asyncio
import os
from dotenv import load_dotenv
from composio import Composio
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerStreamableHTTP

load_dotenv()

What's happening:

We load environment variables and import required modules
Composio manages connections to incident.io
MCPServerStreamableHTTP connects to the incident.io MCP server endpoint
Agent from Pydantic AI lets you define and run the AI assistant

Create a Tool Router Session

python

async def main():
    api_key = os.getenv("COMPOSIO_API_KEY")
    user_id = os.getenv("USER_ID")
    if not api_key or not user_id:
        raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment")

    # Create a Composio Tool Router session for incident.io
    composio = Composio(api_key=api_key)
    session = composio.create(
        user_id=user_id,
        toolkits=["incident_io"],
    )
    url = session.mcp.url
    if not url:
        raise ValueError("Composio session did not return an MCP URL")

What's happening:

We're creating a Tool Router session that gives your agent access to incident.io tools
The create method takes the user ID and specifies which toolkits should be available
The returned session.mcp.url is the MCP server URL that your agent will use

Initialize the Pydantic AI Agent

python

# Attach the MCP server to a Pydantic AI Agent
incident_io_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY})
agent = Agent(
    "openai:gpt-5",
    toolsets=[incident_io_mcp],
    instructions=(
        "You are a incident.io assistant. Use incident.io tools to help users "
        "with their requests. Ask clarifying questions when needed."
    ),
)

What's happening:

The MCP client connects to the incident.io endpoint
The agent uses GPT-5 to interpret user commands and perform incident.io operations
The instructions field defines the agent's role and behavior

Build the chat interface

python

# Simple REPL with message history
history = []
print("Chat started! Type 'exit' or 'quit' to end.\n")
print("Try asking the agent to help you with incident.io.\n")

while True:
    user_input = input("You: ").strip()
    if user_input.lower() in {"exit", "quit", "bye"}:
        print("\nGoodbye!")
        break
    if not user_input:
        continue

    print("\nAgent is thinking...\n", flush=True)

    async with agent.run_stream(user_input, message_history=history) as stream_result:
        collected_text = ""
        async for chunk in stream_result.stream_output():
            text_piece = None
            if isinstance(chunk, str):
                text_piece = chunk
            elif hasattr(chunk, "delta") and isinstance(chunk.delta, str):
                text_piece = chunk.delta
            elif hasattr(chunk, "text"):
                text_piece = chunk.text
            if text_piece:
                collected_text += text_piece
        result = stream_result

    print(f"Agent: {collected_text}\n")
    history = result.all_messages()

What's happening:

The agent reads input from the terminal and streams its response
incident.io API calls happen automatically under the hood
The model keeps conversation history to maintain context across turns

Run the application

python

if __name__ == "__main__":
    asyncio.run(main())

What's happening:

The asyncio loop launches the agent and keeps it running until you exit

Complete Code

Here's the complete code to get you started with incident.io and Pydantic AI:

python

import asyncio
import os
from dotenv import load_dotenv
from composio import Composio
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerStreamableHTTP

load_dotenv()

async def main():
    api_key = os.getenv("COMPOSIO_API_KEY")
    user_id = os.getenv("USER_ID")
    if not api_key or not user_id:
        raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment")

    # Create a Composio Tool Router session for incident.io
    composio = Composio(api_key=api_key)
    session = composio.create(
        user_id=user_id,
        toolkits=["incident_io"],
    )
    url = session.mcp.url
    if not url:
        raise ValueError("Composio session did not return an MCP URL")

    # Attach the MCP server to a Pydantic AI Agent
    incident_io_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY})
    agent = Agent(
        "openai:gpt-5",
        toolsets=[incident_io_mcp],
        instructions=(
            "You are a incident.io assistant. Use incident.io tools to help users "
            "with their requests. Ask clarifying questions when needed."
        ),
    )

    # Simple REPL with message history
    history = []
    print("Chat started! Type 'exit' or 'quit' to end.\n")
    print("Try asking the agent to help you with incident.io.\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "bye"}:
            print("\nGoodbye!")
            break
        if not user_input:
            continue

        print("\nAgent is thinking...\n", flush=True)

        async with agent.run_stream(user_input, message_history=history) as stream_result:
            collected_text = ""
            async for chunk in stream_result.stream_output():
                text_piece = None
                if isinstance(chunk, str):
                    text_piece = chunk
                elif hasattr(chunk, "delta") and isinstance(chunk.delta, str):
                    text_piece = chunk.delta
                elif hasattr(chunk, "text"):
                    text_piece = chunk.text
                if text_piece:
                    collected_text += text_piece
            result = stream_result

        print(f"Agent: {collected_text}\n")
        history = result.all_messages()

if __name__ == "__main__":
    asyncio.run(main())

Conclusion

You've built a Pydantic AI agent that can interact with incident.io through Composio's Tool Router. With this setup, your agent can perform real incident.io actions through natural language. You can extend this further by:

Adding other toolkits like Gmail, HubSpot, or Salesforce
Building a web-based chat interface around this agent
Using multiple MCP endpoints to enable cross-app workflows (for example, Gmail + incident.io for workflow automation)

This architecture makes your AI agent "agent-native", able to securely use APIs in a unified, composable way without custom integrations.

How to build incident.io MCP Agent with another framework

OpenAI Agents SDK

Use incident.io MCP with OpenAI Agents SDK

Claude Agent SDK

Use incident.io MCP with Claude Agent SDK

Google ADK

Use incident.io MCP with Google ADK

LangChain

Use incident.io MCP with LangChain

Vercel AI SDK

Use incident.io MCP with Vercel AI SDK

Mastra AI

Use incident.io MCP with Mastra AI

LlamaIndex

Use incident.io MCP with LlamaIndex

CrewAI

Use incident.io MCP with CrewAI

Claude Code

Use incident.io MCP with Claude Code

Codex

Use incident.io MCP with Codex

Explore Other Toolkits

Addressfinder

Api Key

Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.

Agiled

API Key

Agiled is an all-in-one business management platform for CRM, projects, and finance. It helps you streamline workflows, consolidate client data, and manage business processes in one place.

Airtable

OAuth2Bearer TokenAPI Key

Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations.

TOOLKIT MARKETPLACE

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

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

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

Harsha GaddipatiCo-founder, Slashy

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

Abhi AryaCo-founder, Opennote

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 has immensely helped in keeping new users on the platform.

Nirman DaveCEO, Zams

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

Ryan YuFounder, Extra Thursday

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

Tomisin JenrolaFounder & CEO, SwarmZero

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

Jerome LeclancheCo-Founder, Ingram Technologies

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.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

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.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

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.

How to integrate incident.io MCP with Pydantic AI

Table of Contents

Connect incident.io without Auth hassles

Introduction

TL;DR

What is Pydantic AI?

What is the incident.io MCP server, and what's possible with it?

Supported Tools & Triggers

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

What is Tool Router?

How the Tool Router works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI and Composio

Install dependencies

Set up environment variables

Import dependencies

Create a Tool Router Session

Initialize the Pydantic AI Agent

Build the chat interface

Run the application

Complete Code

Conclusion

How to build incident.io MCP Agent with another framework

OpenAI Agents SDK

Claude Agent SDK

Google ADK

LangChain

Vercel AI SDK

Mastra AI

LlamaIndex

CrewAI

Claude Code

Codex

Explore Other Toolkits

Addressfinder

Agiled

Airtable

FAQ

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

Can I use Tool Router MCP with Pydantic AI?

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

How safe is my data with Composio Tool Router?

Used by agents from

Never worry about agent reliability