Skip to main content
Glama
eLyiN

Codex Bridge

by eLyiN
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CODEX_TIMEOUTNoTimeout in seconds for Codex CLI operations (recommended: 60-120 seconds for most queries, 120-300 for large file analysis)90

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
consult_codexA
Consult Codex in non-interactive mode with structured output.

Processes prompt and returns formatted response.
Supports text, JSON, and code extraction formats.

Args:
    query: The prompt to send to Codex
    directory: Working directory (required)
    format: Output format - "text", "json", or "code" (default: "json")
    timeout: Optional timeout in seconds (overrides env var, recommended: 60-120)
    
Returns:
    Formatted response based on format parameter
consult_codex_with_stdinA
Consult Codex with stdin content piped to prompt - pipeline-friendly execution.

Similar to 'echo "content" | codex exec "prompt"' - combines stdin with prompt.
Perfect for CI/CD workflows where you pipe file contents to the AI.

Args:
    stdin_content: Content to pipe as stdin (e.g., file contents, diff, logs)
    prompt: The prompt to process the stdin content
    directory: Working directory (required)
    format: Output format - "text", "json", or "code" (default: "json")
    timeout: Optional timeout in seconds (overrides env var, recommended: 60-120)
    
Returns:
    Formatted response based on format parameter
consult_codex_batchA
Consult multiple Codex queries in batch - perfect for CI/CD automation.

Processes multiple prompts and returns consolidated JSON output.
Each query can have individual timeout and format preferences.

Args:
    queries: List of query dictionaries with keys: 'query' (required), 'timeout' (optional)
    directory: Working directory (required)
    format: Output format - currently only "json" supported for batch
    
Returns:
    JSON array with all results

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.2/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct purpose: single query, batch processing, and stdin-based interaction. No overlap in functionality, and the parameters clearly differentiate use cases.

Naming Consistency5/5

All tools follow the 'consult_codex' prefix with a clear suffix indicating variant (_batch, _with_stdin). Consistent snake_case with no deviations.

Tool Count5/5

Three tools cover the essential modes of operation (single, batch, stdin) for a Codex bridge server. The count is well-scoped and appropriate for the domain.

Completeness5/5

The tool surface covers all non-interactive consultation modes: single queries, batch processing for CI/CD, and stdin piping. No obvious gaps given the stated non-interactive scope.

Maintenance

ActivityInactive
ResponsivenessSlow

Resources