Skip to main content
Glama
Sign In
claude-codex-bridge

claude-codex-bridge

by umum-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to claude-codex-bridge

No user-submitted related servers found.

    Related Servers

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool targets a distinct lifecycle operation: start (new thread), resume (reattach saved thread), message (continue/idle turn), stop (interrupt), status, events, answer, and models. The main overlap risk is between codex_status and codex_events, both of which read state, but descriptions differentiate session state vs. event journal.

    Naming Consistency5/5

    Every tool uses the codex_ prefix with a clear snake_case verb/noun form (codex_start, codex_message, codex_events, codex_stop). The pattern is uniform and highly predictable.

    Tool Count5/5

    Eight tools is well-scoped for an agent-bridge server covering session lifecycle, messaging, event retrieval, and model listing. Each tool appears to earn its place without redundancy.

    Completeness4/5

    The surface covers the full lifecycle: start, resume, message, stop, status, events, answer, and models. Minor gaps exist, such as explicit session teardown/cleanup or listing historical threads beyond resume, but core workflows are covered.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources