How to integrate Instatus MCP with Codex

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

Instatus logoInstatus
Api Key

Instatus is a status page and incident communication platform for service health, incidents, maintenance, monitors, and subscribers. Use it to keep customers informed during outages, planned work, and live service updates.

15 Tools

Introduction

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

Also integrate Instatus 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 Instatus 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 Instatus MCP server, and what's possible with it?

The Instatus MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Instatus account. It provides structured and secure access to your status pages, components, incidents, maintenance, and service health, so your agent can monitor components, report incidents, publish updates, schedule maintenance, and review service history on your behalf.

  • Status page and service visibility: Have your agent list your status pages, review their components, and check the current health and configuration of a specific service.
  • Incident communication: Let the agent create incidents, review affected components and update history, edit incident details, and publish lifecycle updates as conditions change.
  • Maintenance planning: Direct your agent to schedule or start maintenance, inspect planned and past work, revise schedules and public messages, and post progress updates.
  • Component management: Instruct your agent to create status page components and update their health or presentation when service conditions change.
  • Operational history review: Have your agent list incidents and maintenance events to help your team understand recent disruptions, planned work, and current service status.

Conclusion

You've successfully integrated Instatus with Codex using Composio's MCP server. Now you can interact with Instatus 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 Instatus 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 Instatus operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities
TOOLS

Supported Tools

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

Add Incident Update

Post a public lifecycle update to an Instatus incident and change affected component states.

Add Maintenance Update

Post a public progress update to an Instatus maintenance, optionally changing its lifecycle, timing, and affected component states.

Create Component

Create a component on an Instatus status page.

Create Incident

Create an incident on an Instatus status page with optional affected component states.

Create Maintenance

Schedule or start a maintenance on an Instatus status page.

Get Component

Get the current health and configuration of one component on an Instatus status page.

Get Incident

Get one Instatus incident with its affected components and update history.

Get Maintenance

Get one Instatus maintenance with its schedule, affected components, automation settings, and update history.

List Components

List components and their current health for one Instatus status page, including child components where present.

List Incidents

List incidents for an Instatus status page, optionally including or excluding lifecycle statuses.

List Maintenances

List scheduled and historical maintenances for an Instatus status page.

List Status Pages

List status pages available to the connected Instatus account so an agent can discover page IDs for component, incident, and maintenance operations.

Update Component

Change a component's health or presentation on an Instatus status page.

Update Incident

Edit an existing Instatus incident's name, timing, lifecycle status, affected components, or component states.

Update Maintenance

Fully replace an Instatus maintenance's public message, schedule, lifecycle state, affected components and states, and automation settings.

FAQ

Frequently asked questions

With a standalone Instatus MCP server, the agents and LLMs can only access a fixed set of Instatus tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Instatus 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 Instatus tools.

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

Start with Instatus.It takes 30 seconds.

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

Start building