OpenCodex Quota MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_provider_quotasA | 查询本机 OpenCodex 各提供商的额度、余额、剩余比例、重置时间和数据更新时间。Read provider quotas from the local dashboard. Omit provider to list all. Missing quota means unavailable or unsupported, never zero usage. Uses dashboard caching; does not force refresh or send model completions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.