OpenAI Codex

What You'll Get

Step 1: Add the MCP Server

Before you begin, you'll need a Stable Baseline API key. Visit the MCP Setup Guide to create one from your workspace settings.

First, set your API key as an environment variable by adding it to your shell profile (~/.bashrc, ~/.zshrc, etc.):

export STABLE_BASELINE_API_KEY="your_api_key_here"

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

codex mcp list

[mcp_servers.stablebaseline-mcp]
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 2: Generate Your Documentation

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

Run the sb-setup prompt from the stablebaseline-mcp server

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

What it does

The sb-setup prompt runs a 9-step process:

1. Verifies MCP Connection — Confirms the Stable Baseline server is reachable and authenticated
2. Resolves Workspace & Project — Finds or creates your Stable Baseline workspace and project
3. Scans Your Codebase — Analyzes project structure, tech stack, dependencies, and architecture
4. Checks for Existing Docs — Detects if documentation already exists in Stable Baseline and offers to augment, replace, or cancel
5. Creates Folder Structure — Organizes documentation into logical folders matching your codebase
6. Generates Documents — Writes comprehensive docs for each area of your codebase
7. Adds Diagrams — Creates architecture and flow diagrams using Mermaid, PlantUML, or other supported formats
8. Configures AGENTS.md — Adds auto-sync rules to your project's AGENTS.md file (augments existing content — never removes what's already there)
9. Summary & Next Steps — Provides a summary of everything created with links to view in Stable Baseline

What Gets Documented

The exact documentation 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 will contain rules that tell Codex when to update documentation.

Whenever Codex modifies files matching these patterns, it will automatically update the corresponding Stable Baseline documentation using 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 example prompts in Codex:

Regenerate Documentation

To regenerate your entire documentation from scratch:

Run the sb-setup prompt from the stablebaseline-mcp server

The setup process 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 stablebaseline-mcp

# Remove a server
codex mcp remove stablebaseline-mcp

Other Prompts Available