Skip to main content
Glama
codex-quota-guard-mcp

codex-quota-guard-mcp

by valentine-89

Related Servers

Alternatives to codex-quota-guard-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Adds guardrails around delegating tasks to OpenAI Codex, including quota preflight and handoffs, git worktree isolation, per-turn checkpoints and restore, read-only cross-reviews, and honest failure reporting.
      10
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Routes multiple ChatGPT chats to allowlisted Git workspaces through a single MCP endpoint, and manages persistent Pi and Codex agent pools for coordinated, checkpointed work.
      13
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables Claude Code and Codex to turn an ordinary conversation into an orchestrator that spawns, names, monitors, and revives separate work sessions, aggregates their questions for a single confirmation, and throttles parallelism based on memory and usage limits. Reports results back as a summary table without needing any extra app, daemon, or tmux.
      12
      MIT

    TDQS

    A3.6/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool targets a distinct action: reading quota status, preflight-gating expensive jobs, persisting checkpoints, reading checkpoints, and handling deferral. quota_status and job_preflight both relate to quota state, but their roles as snapshot reader versus execution gate are clear from the descriptions.

    Naming Consistency3/5

    All names are lowercase snake_case and readable, but they mix conventions: quota_status and job_preflight are noun_noun, checkpoint_create and checkpoint_get are noun_verb, and defer_until_reset is a verb phrase. The inconsistency is noticeable but not chaotic.

    Tool Count5/5

    Five tools is well-scoped for a quota-guard server. Each tool covers a necessary part of the workflow without redundancy, and the count feels appropriately minimal rather than padded.

    Completeness4/5

    The core lifecycle is covered: status checking, preflight gating, checkpoint persistence/retrieval, and deferral handling. Minor gaps like checkpoint deletion/update, listing checkpoints, or an explicit reset/release action are absent, but they are not essential to the server's stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues