Skip to main content
Glama
redmikarimo

codex-supervisor

by redmikarimo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to codex-supervisor

No user-submitted related servers found.

    Related Servers

    • Lumen Bridge

      diabetic0
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients and external AI supervisors to oversee and steer native Codex sessions through a thin local stdio bridge. It exposes eleven codex_* supervisory tools for tasks such as listing threads, starting turns, observing progress, steering, responding to approvals, interrupting, checkpointing, and rolling over work.
      MIT

    • Grok Plugin Codex

      handong66
      A
      license
      B
      quality
      F
      maintenance
      An MCP server that exposes the local Grok CLI to Codex for bounded repo work, reviews, rescue analysis, adversarial checks, session listing/export, and background job management while keeping Codex hidden context out of scope.
      12
      1
      MIT

    • Agent Bridge

      mafazsyed
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients such as Claude Code and Codex to delegate persistent review or isolated write-mode implementation tasks to locally installed Claude Code or Codex runtimes, then inspect progress, approve or deny individual permission requests, and continue the same native conversation. It also lists live model catalogues, lets callers follow up on saved conversations, and can run independently via its bundled CLI.
      1
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4.1/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct lifecycle moment: start/send create or resume turns, steer mutates an active turn, status/wait/read observe, interrupt cancels, and approvals have dedicated list/resolve tools. Potentially overlapping pairs like send vs steer and status vs read_thread are explicitly disambiguated in their descriptions.

    Naming Consistency5/5

    All tools share the codex_ prefix and use clear action-oriented verbs, with verb_noun forms for list/read/resolve operations. The naming is consistent, predictable, and uniformly snake_case.

    Tool Count5/5

    10 tools is well-scoped for a Codex supervisor, covering turn lifecycle, observation, thread inspection, and approval handling without unnecessary redundancy. Each tool has a clear role in the workflow.

    Completeness4/5

    The surface covers the core workflow: starting, resuming, steering, observing, waiting on, interrupting, and listing threads, plus approval management. Minor gaps exist around deleting threads or resolving unsupported approval types, but agents can complete primary supervision tasks.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources