Skip to main content
Glama
j-pollack

Codex App Server MCP

by j-pollack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Codex App Server MCP

No user-submitted related servers found.

    Related Servers

    • Local Codex Bridge

      xiaozhe611317
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables external AI supervisors to oversee and steer native Codex through MCP, including thread and turn management, observation, interruption, approval responses, runtime status, and checkpointing.
      MIT

    • AgentNave

      TimWongUp
      A
      license
      A
      quality
      A
      maintenance
      Enables agent managers to launch and supervise Antigravity CLI, Claude Code, CodeBuddy Code, or Grok CLI as subagents through local MCP tools for starting, waiting on, and cancelling invocations.
      4
      MIT

    • OpenCode MCP Orchestrator

      Mesya82
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-capable coding assistants to delegate repository investigation, bounded implementation work, and noisy command runs (tests, builds, linters) to sandboxed OpenCode agents. Each role can use an independently selected model, and only concise results are returned to the parent agent, which keeps responsibility for architecture and high-risk operations.
      MIT

    • pi-agent-mcp

      a809384377
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP hosts like Claude Code and Codex to spawn, manage, and interact with persistent, reusable Pi coding-agent sessions, supporting task dispatch, status checks, and session lifecycle control.
      2 npm
      -

    • DZ23 Subagents Universal MCP

      LMPrado-DZ23
      A
      license
      A
      quality
      A
      maintenance
      Enables users to delegate text and code tasks across multiple AI models with automatic failover, maintain shared mission memory and checkpoints across MCP harnesses, and coordinate parallel role-based subagents. It also supports model discovery, provider inventory, health checks, and stdio/HTTP tool access while leaving patches and tests to the harness.
      24
      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.8/5.0

    Scored across 15 tools

    Disambiguation4/5

    The tools cluster into clear lifecycle, control, and observation groups. The closest pairs—agent_send/agent_steer and agent_status/agent_result—have explicit usage guidance that distinguishes them, so an agent can usually select correctly.

    Naming Consistency3/5

    The agent_ prefix is consistent, but the suffix style is mixed: most tools use imperative verbs (start, send, wait), while status, events, and result are nouns, and request_resolve/goal_set reverse the expected verb-noun order. server_info also breaks the agent_ naming pattern, though reasonably for a server-level tool.

    Tool Count5/5

    Fifteen tools is on the higher end but fits the complexity of orchestrating background agent workers. Each tool covers a distinct lifecycle, observation, or control function, and none feels redundant or unnecessary.

    Completeness5/5

    The tool set covers the full agent lifecycle: start, resume, fork, guide, interrupt, observe, wait, collect results, resolve requests, set goals, and archive. There are no obvious dead ends, and every state change has a corresponding way to inspect or move forward.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources