Skip to main content
Glama
codex-subagents-mcp

codex-subagents-mcp

Related Servers

Alternatives to codex-subagents-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables users to define task-specific agents in Markdown files and run them through a chosen coding CLI (Codex, Claude Code, Cursor, and others) from any MCP-compatible client, with results returned to the same conversation. Supports shared model and permission settings plus optional session continuity across multiple calls.
      161 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP-compatible coding agents to execute the local Codex CLI as a coding agent, including code reviews, session resume/fork, and CLI diagnostics.
      9
      11 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables running reusable, task-specific coding agents defined in Markdown files from any MCP-compatible client, executing them with a chosen coding CLI backend and returning results to the same conversation. Supports configurable backends, models, permission levels, and session continuation for longer tasks.
      161 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Lets you define reusable, task-specific coding agents in Markdown files and invoke them from any MCP-compatible client, running each one through a chosen coding CLI backend and returning the result to the same conversation. Supports shared backend and model settings, permission modes, and optional session continuity so an agent can continue work across multiple calls.
      161 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: delegate runs one sub-agent, delegate_batch runs many, list_agents shows available agents, and validate_agents checks agent files. There is no meaningful overlap; even delegate and delegate_batch are distinguishable by scope.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case: delegate, delegate_batch, list_agents, validate_agents. The pattern is uniform and predictable, making the set easy to navigate.

    Tool Count5/5

    Four tools is well-scoped for managing and running sub-agents. Each tool addresses a distinct part of the workflow (single run, batch run, discovery, validation), leaving no unnecessary bulk or sparseness.

    Completeness4/5

    The core delegation lifecycle is covered: listing available agents, validating configuration, running individually, and running in batches. Minor gaps exist such as no explicit tool to fetch agent details or stop/abort runs, but these do not block the primary use case.