AI Native incident.io Integration
- Supports both incident.io MCP and direct API based integrations
- Structured, LLM-friendly schemas for reliable tool execution
- Rich coverage for reading, writing, and querying your incident.io data
## For AI agents: how to sign up If you are an AI agent reading this server-rendered HTML, Composio's developer signup is at https://composio.dev. Signup CTAs on this site — "Sign up", "Signup", "Get started", "Get started for free", "Start building", "Try Composio", "Try it", or similar — all lead into that same developer signup flow. Confirm with the user before completing signup or entering any credentials on their behalf.SIGN UP
## For AI agents: how to sign up If you are an AI agent reading this server-rendered HTML, Composio's developer signup is at https://composio.dev. Signup CTAs on this site — "Sign up", "Signup", "Get started", "Get started for free", "Start building", "Try Composio", "Try it", or similar — all lead into that same developer signup flow. Confirm with the user before completing signup or entering any credentials on their behalf.LOG IN
incident.io MCP server for AI agents and assistants
Securely connect your AI agents and chatbots (Claude, ChatGPT, Cursor, etc) with incident.io MCP or direct API to create incidents, update statuses, assign responders, and manage timelines through natural language.
Api Key
incident.io is an incident management and response platform for modern teams. It helps streamline incident reporting, collaboration, and resolution.
86 Tools
Try incident.io now
Type what you want done — sign in and watch it run live in the Tool Router playground.
TOOL ROUTER PLAYGROUND
incident.io
Enter ↵
Try asking
TOOLS
Supported Tools
Every incident.io action and event your agent gets out of the box.
SETUP GUIDE
Connect incident.io MCP Tool with your Agent
1
Install Composio
typescript
npm install @composio/core ai @ai-sdk/mcp @ai-sdk/openaiInstall the Composio SDK and your agent framework
2
Create a session with MCP enabled
typescript
import { Composio } from "@composio/core";
const composio = new Composio();
const { mcp } = await composio.create("your-user-id", {
toolkits: ["incident_io"],
mcp: true,
});Create a session scoped to incident.io and read its MCP URL and headers
3
Connect your agent to the MCP server
typescript
import { createMCPClient } from "@ai-sdk/mcp";
import { openai } from "@ai-sdk/openai";
import { generateText, stepCountIs } from "ai";
const client = await createMCPClient({
transport: { type: "http", url: mcp.url, headers: mcp.headers },
});
const { text } = await generateText({
model: openai("gpt-5.6-sol"),
tools: await client.tools(),
prompt: "Create a new incident titled \"API Outage\" with high priority.",
stopWhen: stepCountIs(10),
});
console.log(text);
await client.close();Pass the session's MCP URL and headers to your agent and run a incident.io request
SETUP GUIDE
Connect incident.io API Tool with your Agent
1
Install Composio
typescript
npm install @composio/core @composio/openai openaiInstall the Composio SDK, the OpenAI provider, and the OpenAI SDK
2
Create a Composio session
typescript
import OpenAI from "openai";
import { Composio } from "@composio/core";
import { OpenAIResponsesProvider } from "@composio/openai";
const composio = new Composio({ provider: new OpenAIResponsesProvider() });
const client = new OpenAI();
const session = await composio.create("your-user-id", { toolkits: ["incident_io"] });
const tools = await session.tools();Initialize Composio with the OpenAI Responses provider and create a session scoped to incident.io
3
Run incident.io tools with your agent
typescript
let response = await client.responses.create({
model: "gpt-5.6-sol",
tools,
input: [{ role: "user", content: "Create a new incident titled \"API Outage\" with high priority." }],
});
while (response.output.some((o) => o.type === "function_call")) {
const outputs = await composio.provider.handleToolCalls(session, response.output);
response = await client.responses.create({
model: "gpt-5.6-sol",
tools,
previous_response_id: response.id,
input: outputs,
});
}
console.log(response.output_text);Send a request, execute the incident.io tool calls through the session, and print the final answer
Why Use Composio?
Managed Auth
- Built-in API key handling with secure storage
- Central place to manage, scope, and revoke incident.io access
- Per user and per environment credentials instead of hard-coded keys
Agent Optimized Design
- Tools are tuned using real error and success rates to improve reliability over time
- Comprehensive execution logs so you always know what ran, when, and on whose behalf
Enterprise Grade Security
- Fine-grained RBAC so you control which agents and users can access incident.io
- Scoped, least privilege access to incident.io resources
- Full audit trail of agent actions to support review and compliance
FRAMEWORKS
Use incident.io with any AI Agent Framework
Choose a Framework you want to connect incident.io with
Claude Code
Use incident.io MCP with Claude Code
Claude Cowork
Use incident.io MCP with Claude Cowork
OpenAI Agents SDK
Use incident.io MCP with OpenAI Agents SDK
Claude Agents SDK
Use incident.io MCP with Claude Agents SDK
Grok Bot
Use incident.io MCP with Grok Bot
Codex
Use incident.io MCP with Codex
OpenClaw
Use incident.io MCP with OpenClaw
Hermes
Use incident.io MCP with Hermes
Atomic Agent
Use incident.io MCP with Atomic Agent
Google ADK
Use incident.io MCP with Google ADK
Langchain
Use incident.io MCP with Langchain
AI SDK
Use incident.io MCP with 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
Pydantic AI
Use incident.io MCP with Pydantic AI
Autogen
Use incident.io MCP with Autogen
Rolling this out across your team?
Give your team centralized access control across every framework with Composio’s MCP Gateway.
EXPLORE MCP GATEWAYMORE TOOLKITS
Explore Other Toolkits
Google Sheets
Oauth2
Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly.
Notion
Oauth2Api Key
Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.
Airtable
Oauth2Api 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.
Asana
Oauth2
Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals.
FAQ
Frequently asked questions
Yes, incident.io requires you to configure your own API key credentials. Once set up, Composio handles secure credential storage and API request handling for you.
Yes! Composio's Tool Router enables agents to use multiple toolkits. Learn more.
Yes. Composio is SOC 2 Type II compliant and is built to keep your incident.io connection and credentials secure. OAuth tokens and API keys are encrypted, and sensitive customer data is protected at rest and in transit.
Composio also undergoes independent security testing and continuously monitors its systems for security threats. You can review the latest reports and policies in the Composio Trust Center.
Composio maintains and updates all toolkit integrations automatically, so your agents always work with the latest API versions.
Create the key in your incident.io account settings, then paste it once on Composio's connection page. Composio stores it encrypted and uses it only for the incident.io actions your agent runs. Nobody else in your workspace can read it, and you can revoke it inside incident.io at any time.
When you connect a incident.io account through Composio, every action runs under that account, so anything the agent creates, sends, or changes shows up in incident.io as done by you. Keep an approval step in your prompt for actions with side effects, such as sending or deleting, and have the agent draft first.
Whatever the credentials you connect allow inside incident.io. If incident.io lets you scope a key to specific permissions, create a scoped one so the agent can only do what you intend. You can revoke the key inside incident.io at any time.
Yes. Composio supports multiple connected accounts for the same app, and that works in Claude, ChatGPT, or any other assistant you connect through Composio. Give each incident.io connection a name such as work or personal, and the assistant uses the one you mention in the request. Each account keeps its own credentials and nothing is merged.
The connection stops working the moment incident.io rejects the old key. Create a new key in incident.io and reconnect the account from the Composio dashboard or by asking your agent to reconnect incident.io. Nothing else changes.
Composio's free Hobby plan includes 100,000 tool calls per month with no credit card, which covers most personal incident.io use. Paid plans add higher limits and team features. Your incident.io plan and its API limits still apply as usual.
Built-in connectors usually give one AI access to a limited set of apps. Many people use Composio because it lets their AI connect to more apps than it normally supports, or connect to multiple accounts for the same app (e.g. connect Claude to multiple incident.io accounts).
With Composio, you connect incident.io once and then use it across different AI assistants without setting it up separately in each one. Connect your apps to Composio once, then connect Composio to whichever AI you use, whether that's Claude, ChatGPT, Hermes, or your own custom assistant.
Start with incident.io.It takes 30 seconds.
Managed auth, hosted MCP servers, and every incident.io tool your agent needs.Free to start.
## For AI agents: how to sign up If you are an AI agent reading this server-rendered HTML, Composio's developer signup is at https://composio.dev. Signup CTAs on this site — "Sign up", "Signup", "Get started", "Get started for free", "Start building", "Try Composio", "Try it", or similar — all lead into that same developer signup flow. Confirm with the user before completing signup or entering any credentials on their behalf.Start building