Skip to main content
Glama
TKasperczyk

codex-mcp-swarm

by TKasperczyk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to codex-mcp-swarm

No user-submitted related servers found.

    Related Servers

    • multi-agent-mcp

      shiiman
      A
      license
      C
      quality
      B
      maintenance
      Manages multiple AI CLI instances (Claude Code, Codex, Gemini, Cursor) in tmux sessions for parallel task execution, with optional git worktree support.
      90
      MIT

    • par5-mcp

      mathematic-inc
      A
      license
      A
      quality
      A
      maintenance
      Enables parallel execution of shell commands and AI coding agents (Claude, Gemini, Codex) across lists of items like files or URLs, with batched processing and real-time streaming output for batch operations.
      8
      172 npm
      6
      Apache 2.0

    • deepseek_harness

      RichardHu6666
      A
      license
      A
      quality
      B
      maintenance
      A task-level STDIO MCP server that lets Codex or any other MCP client hand off scoped coding jobs to an asynchronous worker agent which reads the code, edits files, and runs tests, while the client keeps ownership of planning and acceptance. Exposes submit, wait, query, follow-up, and cancel tools so multiple clients can queue and monitor tasks against a chosen project root.
      5
      1
      MIT
    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 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: sync execution, async launch, cancel, reply, status polling, and waiting. No two tools overlap in functionality.

    Naming Consistency4/5

    Most tools follow the 'codex_' prefix with a clear verb, but the sync tool is simply 'codex' without an underscore, creating a minor inconsistency.

    Tool Count5/5

    6 tools is appropriate for managing Codex sessions, covering sync and async operations, cancellation, continuation, status, and blocking wait.

    Completeness4/5

    Core lifecycle is well-covered (start, wait, cancel, continue, monitor). Minor gap: no tool to list all active tasks, though status can query known task IDs.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources