chatgpt-quota-mcp
Allows reading your current ChatGPT/Codex quota through your signed-in Codex CLI.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@chatgpt-quota-mcp How much Codex quota do I have left?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ChatGPT Quota MCP
A single local MCP tool that lets ChatGPT read your current ChatGPT/Codex quota through your already signed-in Codex CLI.
ChatGPT
|
Secure MCP Tunnel
|
get_chatgpt_quota (local MCP)
|
codex app-server --stdio
|
account/rateLimits/readWhat it returns
The server exposes one no-argument tool:
get_chatgpt_quota()Example result:
{
"source": "codex_app_server",
"windows": [
{
"name": "primary",
"used_percent": 25.0,
"remaining_percent": 75.0,
"window_minutes": 300,
"resets_at": 1786543200
}
],
"rate_limit_reached_type": null,
"individual_limit": null,
"spend_control_reached": null,
"reset_credits": null
}The tool does not assume that primary means 5-hour or secondary means weekly. It reports the window duration Codex actually returns.
Related MCP server: copilot-status-mcp
Prerequisites
Python 3.11+
Codex CLI available as
codexCodex CLI already signed in to the ChatGPT account whose quota you want to read
Verify the last two with:
command -v codex
codexInstall
git clone https://github.com/komaksym/chatgpt-quota-mcp.git
cd chatgpt-quota-mcp
uv sync --extra devTest the quota locally first
This bypasses MCP and proves that the Codex quota read works on your machine:
uv run python -c 'from chatgpt_quota_mcp.service import get_chatgpt_quota; import json; print(json.dumps(get_chatgpt_quota(), indent=2))'If that prints your quota, the Codex side is working.
Connect it to ChatGPT
OpenAI Secure MCP Tunnel can launch a local stdio MCP command, so this project does not need an HTTP server or public port.
In OpenAI Platform tunnel settings, create a tunnel associated with the ChatGPT workspace you will use and obtain a
tunnel_idplus runtime API key.Install the current
tunnel-clientfrom OpenAI's tunnel settings/download instructions.Configure the tunnel to launch this project's MCP executable:
export CONTROL_PLANE_API_KEY="sk-..."
TUNNEL_ID="tunnel_..."
MCP_COMMAND="$(pwd)/.venv/bin/chatgpt-quota-mcp"
tunnel-client init \
--sample sample_mcp_stdio_local \
--profile chatgpt-quota \
--tunnel-id "$TUNNEL_ID" \
--mcp-command "$MCP_COMMAND"
tunnel-client doctor --profile chatgpt-quota --explain
tunnel-client run --profile chatgpt-quotaDo not commit the runtime API key.
In ChatGPT, enable Settings -> Security and login -> Developer mode.
Open ChatGPT Plugins, press +, choose Tunnel under Connection, and select or paste your
tunnel_id.Confirm that ChatGPT discovers exactly one tool:
get_chatgpt_quota.
Then ask:
How much Codex quota do I have left?
Development
uv sync --extra dev
uv run ruff check .
uv run ruff format --check .
uv run mypy src
uv run pytest
uv buildThe test suite includes a real MCP stdio round trip backed by a fake Codex executable, so CI exercises the full local protocol chain without using a real account.
Why this shape
The Codex App Server has a stable account/rateLimits/read method. Using that structured interface is smaller and less brittle than scraping ChatGPT UI text or calling undocumented ChatGPT backend endpoints.
References
Available Tools
1 toolget_chatgpt_quotaA
Return current ChatGPT/Codex quota windows, remaining usage, and reset times.
Inputs: no named parameters. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
MCP server for OpenAI API (chat completions, image generation, embeddings) via AceDataCloud
A paid remote MCP for OpenAI Codex agent coordination MCP, built to return verdicts, receipts, usage
Analytics for MCP servers. Query your tool calls, first-call success, retries and schema cost.
Hosted MCP server for LLM cost estimation, model comparison, and budget-aware routing.
Related MCP Servers
- AlicenseAqualityFmaintenanceAn MCP server that retrieves current GitHub Copilot usage data, including quotas, limits, and usage statistics. It allows AI agents to monitor premium interaction status and detailed account usage via raw or formatted summaries.39 npmMIT
- AlicenseAqualityCmaintenanceMCP server to check GitHub Copilot quota, rate-limit status, and reset times from any MCP client.130 npmMIT
- AlicenseAqualityCmaintenanceAn MCP server that exposes Claude Code's real-time rate limit usage so that an orchestrator can check remaining capacity before launching subtasks.110 npmMIT
- AlicenseNot gradedqualityBmaintenanceExposes rate-limit and usage data for AI coding agent CLIs as MCP tools, enabling querying of usage snapshots and reset times.MIT