OpenCodex Quota MCP
Related Servers
Alternatives to OpenCodex Quota MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceA read-only MCP server for querying AI provider administration APIs, providing normalized usage, cost, and dashboard data for OpenAI and Anthropic.417 npmMIT
- AlicenseAqualityBmaintenanceA local, read-only MCP server that gives Codex a plan-aware view of its remaining usage and helps choose work that fits the current usage window.21MIT
- FlicenseAqualityDmaintenanceMCP server that exposes a single tool to retrieve ChatGPT/Codex quota via the signed-in Codex CLI, reporting rate-limit windows and usage percentages.1-
- AlicenseNot gradedqualityDmaintenanceMCP server that reads local OpenClaw session files to provide token usage and cost data without any network calls or authentication.MIT
- AlicenseAqualityBmaintenanceCloudOps MCP is a read-only Model Context Protocol server that exposes normalized operational infrastructure context (logs, metrics, deployments, health) to AI agents through a small set of typed, bounded tools.6MIT
- FlicenseNot gradedqualityBmaintenanceRead-only MCP server for querying AI usage metrics (exact tokens, cost, latency, errors, productivity) from a local SQLite database, enabling charts and analysis in Claude Code and Cursor.-
TDQS
Scored across 1 tool
Only one tool exists, so there is no possible overlap or misselection risk. Its purpose (read provider quotas) is stated unambiguously.
Single name get_provider_quotas follows a clean verb_noun snake_case convention that matches what a consistent set would look like. No mixed conventions to worry about.
A single read-only query tool is thin even for a narrow domain; users would expect at least a companion for per-provider detail or a refresh action. It is defensible for a read-only dashboard mirror, but it sits at the borderline of 1-2 tools.
Reading quotas, balances, reset times and update timestamps covers the core read need, with omit-provider listing all. The main gap is the explicit absence of any force-refresh or historical view, so an agent stuck with stale cached data has no escape hatch.