How to integrate iLert MCP with Codex

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

iLert logoiLert
Api Key

iLert is an incident response platform for alerts, on-call schedules, escalations, incidents, and status pages. It helps teams route incidents fast, reduce downtime, and keep users informed.

8 Tools

Introduction

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

Also integrate iLert with

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 1000+ 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 iLert MCP in Codex

Run the setup command

Run this command in your terminal to add the Composio MCP server to Codex.

Terminal

It will initiate the authentication in a browser window, authorize Codex to access your Composio account.

Composio authentication page

(Optional) Authenticate with OAuth

To authenticate manually, run the login command to open a browser window and authorize Codex to access your Composio account.

bash
codex mcp login composio

Verify the connection

Run codex mcp list to confirm Composio appears as a registered MCP server.

bash
codex mcp list

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
  2. Fill the header and Key fields with { "x-consumer-api-key" = "ck_*******" }.
  3. The Key is the Composio API key, that you can find on dashboard.composio.dev
  4. Click on Authenticate and authorize Codex to your Composio account and you're all set.
Codex App MCP setup
  1. Restart and verify if it's there in .codex/config.toml
bash
[mcp_servers.composio]
url = "https://connect.composio.dev/mcp"
http_headers = { "x-consumer-api-key" = "ck_*******" }

What is the iLert MCP server, and what's possible with it?

The iLert MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your iLert account. It provides structured and secure access to your alerts, incidents, on-call schedules, escalation policies, services, teams, and maintenance windows, so your agent can review alerts, track incidents, identify on-call responders, inspect schedules, and browse response resources on your behalf.

  • Alert monitoring: Have your agent list alerts by state, source, escalation policy, responder, or report time, then retrieve the details of a specific alert.
  • Incident tracking: Let the agent list status incidents by lifecycle state, affected service, or report time, and review a specific incident's affected teams and history.
  • On-call coverage: Direct your agent to find who is on call for selected schedules, escalation policies, users, and time windows.
  • Schedule visibility: Instruct your agent to list on-call schedules and review current shifts, upcoming shifts, or schedule definitions.
  • Response resource lookup: Have your agent browse services, teams, escalation policies, and maintenance windows when investigating operational issues.

Conclusion

You've successfully integrated iLert with Codex using Composio's MCP server. Now you can interact with iLert 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 iLert operations
  • Managed authentication through Composio
  • Access to 20,000+ tools across 1000+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

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

Supported Tools

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

Get Alert

Get one iLert alert by its numeric ID, optionally expanding escalation rules, the next escalation user, or custom details.

Get Current User

Return the authenticated iLert user, including identity, role, timezone, and active team context.

Get Incident

Get one iLert status incident by numeric ID, optionally including subscription state, affected teams, or history.

List Alerts

List iLert alerts with optional state, source, escalation-policy, responder, and report-time filters.

List Incidents

List iLert status incidents with optional lifecycle-state, affected-service, and report-time filters.

List On Calls

Find who is on call for selected escalation policies, schedules, users, and a time window of at most three months.

List Resources

List one incident-response resource catalog: services, teams, escalation policies, or maintenance windows.

List Schedules

List iLert on-call schedules, optionally expanding current or next shifts and schedule definitions.

FAQ

Frequently asked questions

With a standalone iLert MCP server, the agents and LLMs can only access a fixed set of iLert tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from iLert and many other apps based on the task at hand, all through a single MCP endpoint.

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 iLert tools.

Yes, absolutely. You can configure which iLert 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 iLert data and credentials are handled as safely as possible.

Start with iLert.It takes 30 seconds.

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

Start building