How to integrate incident.io MCP with Codex

Framework Integration Gradient
incident.io Logo
Codex Logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With incident.io MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or app, whichever you prefer.

Composio removes the Authentication handling completely from you. We handle the entire integration lifecycle, and all you need to do is just copy the URL below, authenticate inside Codex, and start using it.

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 870+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install incident.io MCP in Codex

Codex CLI

Run the command in your terminal.

Terminal

This will auto-redirect you to the Rube authentication page.

Rube authentication redirect page

Once you're authenticated, you will be able to access the tools.

Verify the installation by running:

codex mcp list

If you otherwise prefer to use config.toml, add the following URL to it. You can get the bearer token from rube.app → Use Rube → MCP URL → Generate token

[projects."/home/user/composio"]
trust_level = "untrusted"

[mcp_servers.rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex in VS Code

If you have installed Codex in VS Code.

Then: ⚙️ → MCP Settings → + Add servers → Streamable HTTP:

Add the Rube MCP URL: https://rube.app/mcp and the bearer token.

VS Code MCP Settings

To verify, click on the Open config.toml

Open config toml in Codex

Make sure it's there:

[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
Codex App MCP Settings
  1. Restart and verify if it's there in .codex/config.toml
[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"
  1. Save, restart the extension, and start working.

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.

Conclusion

You've successfully integrated incident.io with Codex using Composio's Rube MCP server. Now you can interact with incident.io directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for incident.io operations
  • Managed authentication through Composio's Rube
  • Access to 20,000+ tools across 870+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various incident.io operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build incident.io MCP Agent with another framework

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 Codex?

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