chatgpt-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_chatgpt_quotaA | Return current ChatGPT/Codex quota windows, remaining usage, and reset times. |
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 possibility of overlap or confusion. The tool's purpose is unambiguous and clearly distinct.
The single tool name 'get_chatgpt_quota' follows a clear verb_noun pattern, consistent with common MCP server conventions. Since there's only one tool, consistency is trivially maintained.
The server has a focused scope on ChatGPT quota; one tool is minimal but appropriate for a read-only quota endpoint. It sits on the low end of typical counts but is not excessive for the stated purpose.
The tool provides a complete picture of quota status including windows, usage, and reset times. For a quota-information server, there are no obvious missing operations.