Codex

Use runStdioMcpServer to expose Corsair as a local MCP server that Codex spawns on demand.

Install

npm install @corsair-dev/mcp

Create the server script

mcp-server.ts

import 'dotenv/config';
import { runStdioMcpServer } from '@corsair-dev/mcp';
import { corsair } from './corsair';

runStdioMcpServer({ corsair }).catch((err) => {
    console.error('[corsair-mcp] Fatal:', err);
    process.exit(1);
});

Configure Codex

Codex reads MCP servers from ~/.codex/config.toml. Add a corsair server:

~/.codex/config.toml

[mcp_servers.corsair]
command = "npx"
args = ["tsx", "mcp-server.ts"]

If your credentials aren’t loaded from a .env file, pass them under an env table:

~/.codex/config.toml

[mcp_servers.corsair]
command = "npx"
args = ["tsx", "mcp-server.ts"]

[mcp_servers.corsair.env]
CORSAIR_KEK = "your-key-here"

Restart Codex after editing the config. Run codex mcp list to confirm corsair is registered.

Usage

Once connected, Codex can call Corsair tools directly:

Setup corsair, then list all Slack channels.

Codex calls list_operations to discover available endpoints, get_schema to inspect parameters, then run_script to execute.

npm install @corsair-dev/cli

yarn add @corsair-dev/cli

pnpm install @corsair-dev/cli

bun add @corsair-dev/cli

Copy and paste this prompt into Codex to give it everything it needs to work with Corsair:

Run `pnpm corsair` to access Corsair's integrations.

Get Started

Frameworks

Adapters

Workflows (beta)

Reference

Install

Create the server script

Configure Codex

Usage

​Install

​Create the server script

​Configure Codex

​Usage

Install

Create the server script

Configure Codex

Usage