Skip to main content
Glama
shilong20

codex-mcp-server

by shilong20
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to codex-mcp-server

No user-submitted related servers found.

    Related Servers

    • hanako-codex-bridge

      TheEarlyWinter
      A
      license
      Not graded
      quality
      B
      maintenance
      A local stdio MCP server that lets Hanako and Codex delegate one-off or persistent text tasks to each other, check local service and executable status, and manage bounded concurrent delegations without exposing tokens or paths.
      MIT

    • Vibechemy

      DiamondAlchemy
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server for orchestrating a fleet of CLI coding agents in isolated git worktrees. It exposes tools for spawning workers, sending instructions, reviewing diffs, and merging changes, with full terminal visibility.
      6 npm
      4
      MIT

    • tmux-mcp

      trolleydodger1988
      F
      license
      A
      quality
      D
      maintenance
      A persistent, stateful MCP server that exposes a detached tmux session to clients, enabling shell command execution, terminal buffer reading, and control signal sending via JSON-RPC over stdio.
      3
      -
    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

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct role: run blocking, run async, check status, cancel. No overlap or ambiguity.

    Naming Consistency4/5

    Three tools use the codex_ prefix (codex_dispatch, codex_status, codex_cancel), while the main tool is just 'codex'. This minor inconsistency is acceptable as the base tool is the primary action.

    Tool Count5/5

    4 tools are well-scoped for managing Codex tasks: execute (sync), dispatch (async), status, cancel. No unnecessary tools.

    Completeness4/5

    Covers core lifecycle (start, background, status, cancel). A resume functionality is hinted via session_id but not a separate tool, which is a minor gap.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources