quota-dashboard-mcp
The quota-dashboard-mcp server provides a local, privacy-first way to monitor AI subscription quotas for Claude Code Max, Kimi, and Z.ai through a unified interface.
get_quota_summary: Retrieve a combined overview of quota usage across all configured providers in a single call. Providers without a configured token report a config error without failing the entire request.get_provider_quota: Query detailed quota information for a single provider (claude,kimi, orzai), with support for an optional bearer token override and amockflag for testing without hitting real APIs.check_quota_health: Get a health report flagging providers that exceed a configurable usage threshold (default 80%) or have missing/invalid tokens, returning actionable warnings to help avoid unexpected quota outages.
Privacy is ensured by reading tokens from environment variables at call time, never persisting them to disk, and only sending them to the provider's own API. The server integrates with MCP-compatible clients like Claude Code, Cursor, and VS Code via stdio transport.
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., "@quota-dashboard-mcp Show my quota summary"
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.
quota-dashboard-mcp
A local-run, privacy-first MCP server that exposes real-time AI subscription quota for Claude Code Max, Kimi, and Z.ai. It uses stdio transport, so it works with Claude Code, Cursor, VS Code, and any other MCP stdio client.
Tokens stay on your machine: they are read from environment variables at call time, never persisted to disk, and never sent anywhere except the provider's own API.
Looking for a GUI? See the sibling project
quota-dashboard.
Tools
Tool | Description |
| Unified quota summary across all configured providers. |
| Detailed quota for one provider ( |
| Flags providers over a usage threshold (default 80%) or missing/invalid tokens. |
Related MCP server: minimax-remaining-mcp
Install
Requirements
Node.js ≥ 18
A bearer token for each provider you want to query (see Token setup below)
One-line install
The package is installable directly from GitHub today (no npm account required):
npx -y ryan-knowone/quota-dashboard-mcpOnce the package is published to npm, the canonical command will be:
npx -y quota-dashboard-mcp@latestClaude Code
Add the server to your Claude Code config (~/.claude/CONFIG.json or via /mcp):
{
"mcpServers": {
"quota-dashboard": {
"command": "npx",
"args": ["-y", "ryan-knowone/quota-dashboard-mcp"],
"env": {
"CLAUDE_TOKEN": "your_claude_oauth_token",
"KIMI_TOKEN": "your_kimi_platform_api_key",
"ZAI_TOKEN": "your_zai_bearer_token"
}
}
}
}Cursor
Open Cursor Settings → MCP → Add new MCP server, then paste:
Name:
quota-dashboardType:
commandCommand:
env CLAUDE_TOKEN=your_claude_oauth_token KIMI_TOKEN=your_kimi_platform_api_key ZAI_TOKEN=your_zai_bearer_token npx -y ryan-knowone/quota-dashboard-mcpVS Code
Add to your VS Code settings.json (requires the Claude AI extension or any MCP-compatible extension):
{
"mcp": {
"servers": {
"quota-dashboard": {
"command": "npx",
"args": ["-y", "ryan-knowone/quota-dashboard-mcp"],
"env": {
"CLAUDE_TOKEN": "your_claude_oauth_token",
"KIMI_TOKEN": "your_kimi_platform_api_key",
"ZAI_TOKEN": "your_zai_bearer_token"
}
}
}
}
}Token setup
Claude Code Max
The quota endpoint requires an OAuth token from an authenticated Claude Code browser session. The easiest source is ~/.claude/credentials.json.
The server currently reads CLAUDE_TOKEN from the environment. To extract it:
# macOS
jq -r '.accessToken' ~/Library/Application\ Support/Claude/credentials.json
# Linux
jq -r '.accessToken' ~/.claude/credentials.jsonThen set CLAUDE_TOKEN to that value.
Kimi
Use a platform API key from platform.moonshot.cn. Set it as KIMI_TOKEN.
In practice, the same sk-kimi-... key used by Claude Code's Anthropic-compatible proxy also works for the Kimi usage endpoint. If your proxy key returns Invalid Authentication, create a dedicated platform API key from platform.moonshot.cn.
Z.ai
Use a Bearer token from your Z.ai account/dashboard. Set it as ZAI_TOKEN.
Local development
git clone https://github.com/ryan-knowone/quota-dashboard-mcp.git
cd quota-dashboard-mcp
npm install
# Run directly with tsx
CLAUDE_TOKEN=... KIMI_TOKEN=... ZAI_TOKEN=... npm run dev
# Or build and run
npm run build
CLAUDE_TOKEN=... KIMI_TOKEN=... ZAI_TOKEN=... npm startTesting a tool call
With the server running over stdio, send a JSON-RPC tools/call request:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_provider_quota",
"arguments": { "provider": "kimi", "mock": true }
}
}Privacy
Tokens are read from environment variables at call time.
Tokens are never written to disk (other than the env vars you already manage).
Tokens and usage data are never sent to telemetry or any third party except the provider's own API.
Support
This is an independent open-source project. If it saves you from an unexpected quota outage, you can tip ETH/USDC on Base:
0x1e2D7F8715E8180816c0236A5c4F21596C5b9c9e
Issues and PRs are welcome — provider endpoints change often and community maintenance keeps the tool accurate.
License
MIT
Available Tools
3 toolscheck_quota_healthA
Flags providers that are over a usage threshold (default 80%) or have missing/invalid tokens. Returns a health report with actionable warnings.
Inputs: threshold.
get_provider_quotaB
Returns detailed quota information for a single provider. Supported providers: claude, kimi, zai.
Inputs: provider (required), mock, token.
get_quota_summaryA
Returns a unified quota summary across all configured providers (Claude Code Max, Kimi, Z.ai). Providers without a configured token report a config error rather than failing the whole call.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool serves a distinct purpose: health check, per-provider details, and unified summary. No overlap in functionality.
All tools follow snake_case and a consistent verb_noun pattern (check_quota_health, get_provider_quota, get_quota_summary).
Three tools is appropriate for a quota dashboard, covering health check, per-provider detail, and summary without unnecessary bloat.
Provides essential read operations for quota monitoring. Minor gap: no tool to update thresholds or configure providers, but the domain appears read-only by design.
Maintenance
Related MCP Connectors
AI coding plan limits (Claude Code, Codex, Cursor, Copilot): router, picker, status, budget check
Live status, API pricing and rate limits for ChatGPT, Claude, Gemini, Cursor and 42+ AI tools.
Track API spend, credit balances and runway across OpenAI, Anthropic, OpenRouter and 25 more.
Live status and health checks for AI coding providers: Claude, Cursor, Copilot, Codex and more.
Related MCP Servers
- AlicenseAqualityNot gradedmaintenanceProvides real-time visibility into Claude Pro and Max subscription usage limits directly within Claude Code by utilizing local OAuth tokens. It enables users to monitor session and weekly usage across different models and receive alerts regarding rate-limiting status.4-
- AlicenseAqualityDmaintenanceLets AI agents check remaining MiniMax Token Plan quota and automatically pause themselves before hitting rate limits.8MIT
- AlicenseAqualityDmaintenanceEnables querying OpenCode Go subscription quota (rolling, weekly, and monthly usage) and Zen prepaid balance as MCP tools.217 npmMIT
- AlicenseAqualityCmaintenanceLets an AI agent check its own Claude and Codex usage limits — used percentages and exact reset times for session and weekly windows — so it can plan long-running work around resets instead of dying mid-task. It reads local, credential-free sources by default, always reports which source answered, and ships a hook that pushes quota state into context automatically.1MIT