OpenAI Codex with Stable Baseline.

Before you begin

You'll need a Stable Baseline API key. Visit the MCP setup guide to create one from your workspace settings. Keys are prefixed sta_… and shown only once.

Step 1 · Export your API key

Codex reads bearer tokens from your environment at runtime — the token itself never sits in a config file. Add the export to your shell profile (~/.bashrc, ~/.zshrc, etc.):

export STABLE_BASELINE_API_KEY="sta_your_api_key_here"

Step 2 · Option A: via the Codex CLI (recommended)

codex mcp add sb \
  --url "https://api.stablebaseline.io/functions/v1/cloud-serve/mcp" \
  --bearer-token-env-var STABLE_BASELINE_API_KEY

Verify the server was added:

codex mcp list

Step 2 · Option B: edit the config file directly

Open (or create) the config at ~/.codex/config.toml and add:

[mcp_servers.sb]
url = "https://api.stablebaseline.io/functions/v1/cloud-serve/mcp"
bearer_token_env_var = "STABLE_BASELINE_API_KEY"
http_headers = {}
startup_timeout_sec = 30
tool_timeout_sec = 60
enabled = true

After adding the server, restart Codex or start a new session. The server will connect automatically.

Step 3 · Generate your documentation

Once the MCP server is connected, start Codex and type:

Run the sb-setup prompt from the sb server

Codex walks you through an interactive setup process to generate documentation for your project.

What sb-setup does — the 9-step process

• Verifies MCP connection — Confirms the Stable Baseline server is reachable and authenticated
• Resolves workspace & project — Finds or creates your Stable Baseline workspace and project
• Scans your codebase — Analyses project structure, tech stack, dependencies, and architecture
• Checks for existing docs — Detects if documentation already exists in Stable Baseline and offers to augment, replace, or cancel
• Creates folder structure — Organises documentation into logical folders matching your codebase
• Generates documents — Writes comprehensive docs for each area of your codebase
• Adds diagrams — Creates architecture and flow diagrams using Mermaid, PlantUML, or other supported formats
• Configures AGENTS.md — Adds auto-sync rules to your project's AGENTS.md file (augments existing content — never removes what's already there)
• Summary & next steps — Provides a summary of everything created with links to view in Stable Baseline

What gets documented

• Architecture — High-level system design, component relationships, data flow
• API & Integrations — Endpoints, external services, authentication flows
• Data Model — Database schemas, relationships, migrations
• Frontend — Component hierarchy, state management, routing
• Backend — Server logic, middleware, business rules
• DevOps — Build pipeline, deployment, environment configuration
• Auth & Identity — Authentication, authorisation, user management

The exact structure is determined dynamically based on your codebase — no two projects get the same output.

How auto-sync works

After setup, your AGENTS.md file contains rules that tell Codex when to update documentation:

Whenever Codex modifies files matching these patterns, it automatically updates the corresponding Stable Baseline documentation via the sb-sync prompt.

File structure

Your Stable Baseline Project
├── Architecture/
│   ├── High Level Overview
│   └── System Architecture Diagram
├── Frontend/
│   ├── Component Hierarchy
│   ├── State Management
│   └── Routing & Navigation
├── Backend/
│   ├── API Endpoints
│   ├── Business Logic
│   └── Middleware & Auth
├── Data Model/
│   ├── Database Schema
│   └── Entity Relationships
└── DevOps/
    ├── Build & Deploy
    └── Environment Config

This is an example. Your actual structure will be tailored to your specific project.

Try it

Once setup is complete, try these prompts in Codex:

Regenerate documentation

To regenerate your entire documentation from scratch:

Run the sb-setup prompt from the sb server

Setup will detect existing documentation and ask whether you want to augment (add to existing), replace (start fresh), or cancel.

Managing MCP servers

Codex provides CLI commands to manage your MCP server connections:

# List all configured servers
codex mcp list

# View details of a specific server
codex mcp get sb

# Remove a server
codex mcp remove sb

Other prompts available