How to integrate Better stack MCP with Codex

Better stack logo
Codex logo
divider

Introduction

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

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

The Better stack MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Better Stack account. It provides structured and secure access to your monitoring, logging, and incident management tools, so your agent can perform actions like retrieving uptime metrics, managing escalation policies, checking heartbeat statuses, and organizing log sources on your behalf.

  • Monitor health checks and availability: Let your agent fetch uptime percentages, availability summaries, and incident details for any monitor in your stack.
  • Automated escalation policy management: Instruct your agent to create or delete escalation policies, keeping your incident response workflows up-to-date without manual effort.
  • Heartbeat tracking and organization: Have your agent fetch specific heartbeat data, check heartbeat availability, or group related heartbeats for easier monitoring.
  • Log source grouping and management: Enable your agent to create or delete source groups, helping you organize log streams and maintain a tidy observability structure.
  • Webhook integration setup: Direct your agent to register outgoing webhooks so your stack can notify external systems of important events automatically.

Supported Tools & Triggers

Tools
Create Escalation PolicyTool to create a new escalation policy.
Create Heartbeat GroupTool to create a new heartbeat group.
Create Outgoing Webhook IntegrationTool to create a new outgoing webhook integration.
Create Source GroupTool to create a new source group.
Delete Escalation PolicyTool to delete an escalation policy by id.
Delete Source GroupTool to delete a source group by id.
Get HeartbeatTool to get a single heartbeat by id.
Get Heartbeat AvailabilityTool to retrieve availability summary for a specific heartbeat.
Get MonitorTool to get a single monitor.
Get Monitor AvailabilityTool to return an availability summary for a specific monitor.
Get Monitor Response TimesTool to return response times for a specific monitor.
Get Status PageTool to get a single status page by id.
Get Telemetry API TokenTool to retrieve the telemetry api token from the integration configuration.
Get Uptime API TokenTool to retrieve the configured uptime api token.
List Catalog RelationsTool to list all catalog relations.
List Google Monitoring IntegrationsTool to list all google monitoring integrations.
List Grafana IntegrationsTool to list all grafana integrations.
List HeartbeatsTool to list all heartbeats.
List MonitorsTool to list all monitors.
List New Relic IntegrationsTool to list new relic integrations.
List On-Call SchedulesTool to list all on-call schedules.
List Status Page ReportsTool to list all reports on a status page.
List Status PagesTool to list all your status pages.
Update HeartbeatTool to update an existing heartbeat configuration.
Update Heartbeat GroupTool to update an existing heartbeat group.
Update Source GroupTool to update an existing source group.

Conclusion

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

How to build Better stack MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Better stack MCP?

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

Can I manage the permissions and scopes for Better stack while using Tool Router?

Yes, absolutely. You can configure which Better stack 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 Better stack 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.