Skip to main content
Glama
naowalrahman

codex-monitor

by naowalrahman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to codex-monitor

No user-submitted related servers found.

    Related Servers

    • Codex Conductor

      yksanjo
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that allows AI agents to monitor and interact with Codex sessions, providing session awareness, status summaries, and managed tmux windows for automated continuation.
      1
      MIT

    • mcp-codex-dev

      FYZAFH
      A
      license
      A
      quality
      F
      maintenance
      An MCP server that integrates Codex CLI into Claude Code workflows for code writing, execution, and review with session management. It features real-time progress monitoring via a local HTTP dashboard and supports detailed configuration for various coding tools.
      6
      15 npm
      166
      MIT

    • agent-comm

      keshrath
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables AI coding agents to communicate, share state, and coordinate work in real time via MCP tools or REST API.
      202 npm
      5
      MIT

    • Codex Octopus

      xiaolai
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that wraps the OpenAI Codex SDK to deploy multiple specialized AI agents with individual configurations for models, sandboxing, and behavior. It enables users to manage dedicated tools for tasks like code review and test writing through a customizable agent factory.
      2
      45 npm
      19
      ISC

    • mcp-gauge

      sogawa-yk
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables coding agents to autonomously test, evaluate, and tune other MCP servers by acting as a proxy and providing linting, trace recording, evaluation, comparison, and reporting tools.
      7
      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

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct role in the monitor lifecycle: create, wait, run, status, and cancel. There is no overlap—monitor_run combines create and wait, but it is a convenience wrapper rather than a competing tool.

    Naming Consistency5/5

    All tool names follow the same `monitor_<verb>` pattern, making the action and resource predictable. The verbs are consistent and match the function of each tool.

    Tool Count5/5

    Five tools cover the full monitor workflow without bloat or missing essentials. This is a well-scoped set for a monitoring utility.

    Completeness5/5

    The set provides complete lifecycle coverage: create, wait, cancel, status, and a combined create-and-wait convenience. There are no obvious dead ends—a user can create, monitor, and clean up monitors with these tools.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources