codex-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEX_MODEL | No | Default model override (alternative to CODEX_BRIDGE_MODEL) | gpt-5.3-codex |
| CODEX_BRIDGE_MODEL | No | Default model override | gpt-5.3-codex |
| CODEX_BRIDGE_RETRIES | No | Transient retry count | 1 |
| CODEX_BRIDGE_MAX_SESSIONS | No | Max in-memory sessions before oldest-session eviction | 200 |
| CODEX_BRIDGE_SESSION_TTL_MS | No | Session inactivity TTL in milliseconds | 86400000 |
| CODEX_BRIDGE_RETRY_BACKOFF_MS | No | Retry backoff base in milliseconds | 500 |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| codex_askA | Ask GPT Codex a question or brainstorm an idea. Codex acts as a critical thinking partner — it will challenge assumptions and surface risks. |
| codex_reviewA | Send code to GPT Codex for critical review. Codex will look for bugs, security issues, performance problems, and design flaws. |
| codex_planA | Collaboratively plan an implementation with GPT Codex. Describe the problem and constraints, get a concrete approach with trade-offs and alternatives. |
| codex_researchA | Deep-dive research via GPT Codex. Multi-turn: Codex surveys the topic, drills into gaps, then synthesizes findings. Can take minutes — trades speed for depth. Use for architecture exploration, library evaluation, or understanding unfamiliar codebases. |
| codex_debugA | Structured root-cause analysis via GPT Codex. Multi-turn: Codex generates hypotheses, tests them against the code and web sources, then delivers a verdict with evidence chain. Can take minutes. Use for hard-to-find bugs, unexpected behavior, or production incidents. |
| codex_risk_radarA | Analyze a git diff to identify risk zones and recommend the right collaboration depth. Returns risk score, affected categories, and whether to use codex_ask, codex_review, or codex_plan+review. |
| codex_statsA | Get round-trip statistics for this session's Claude ↔ Codex collaboration. Shows number of exchanges, latency breakdown, and per-tool usage. |
| codex_sessionsA | List active in-memory sessions with recency and activity summary. Useful when running multiple clients against one bridge process. |
| codex_resetA | Reset the conversation session with Codex. Clears history and stats. Use when starting a new topic. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ndcorder/claude-codex-team'
If you have feedback or need assistance with the MCP directory API, please join our Discord server