codex-quota-guard-mcp
Related Servers
Alternatives to codex-quota-guard-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAdds 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.10MIT
- AlicenseBqualityBmaintenanceEnables governed Codex work sessions by planning bounded segments, maintaining capacity reserves, and creating checkpoint-based resume contracts so long-running jobs can pause and resume deterministically within quota limits.3MIT
- AlicenseNot gradedqualityAmaintenanceA local, repository-scoped MCP coordination bridge that lets Claude Code and Codex work together in the same checkout via tasks, leases, and evidence-based completion, preventing conflicting edits and enabling bounded delegation.1MIT
- AlicenseAqualityDmaintenanceWraps OpenAI's Codex CLI with true parallel task execution, worktree isolation for conflict-free runs, and live monitoring of each task.617MIT
- AlicenseAqualityBmaintenanceRoutes multiple ChatGPT chats to allowlisted Git workspaces through a single MCP endpoint, and manages persistent Pi and Codex agent pools for coordinated, checkpointed work.13MIT
- AlicenseNot gradedqualityBmaintenanceEnables Codex to delegate coding tasks to DeepSeek Harness (DSH) for file reading, editing, and checking, while Codex handles planning and review. It manages scheduled workflows with concurrency safety and acceptance evidence.1MIT
TDQS
Scored across 5 tools
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.
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.
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.
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.