kiro-usage-mcp
Related Servers
Alternatives to kiro-usage-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables read-only viewing of 0G Router account credits and usage across multiple accounts through MCP, exposing status, balances, and model pricing without triggering inference or payments.MIT
- AlicenseNot gradedqualityBmaintenanceExposes rate-limit and usage data for AI coding agent CLIs as MCP tools, enabling querying of usage snapshots and reset times.MIT
- AlicenseAqualityBmaintenanceEnables querying OpenCode Go subscription quota (rolling, weekly, and monthly usage) and Zen prepaid balance as MCP tools.211 npmMIT
- FlicenseNot gradedqualityDmaintenanceMCP server that exposes AI credit usage data from OpenMeter to the TAIS AI chat service, automatically scoped to the calling tenant and restricted to admin users.-
- FlicenseAqualityBmaintenanceMCP 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 gradedqualityCmaintenanceLets Claude look up your own Claude subscription usage limits — the same 5-hour and weekly percentages shown by /usage — mid-conversation, so it can pace long tasks and warn you before you hit a wall. It reads the local OAuth login, serves a throttled read-only snapshot (cached with graceful fallback), and exposes it as a single get_usage tool.MIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of confusion or misselection. Its purpose (fetch Kiro plan credit usage) is unambiguous.
The single name get_kiro_usage follows a clear verb_noun convention with a domain-specific prefix. With only one tool there are no conflicting conventions to reconcile.
The server's scope is narrow — reporting credit usage from kiro-cli — so a single tool is reasonable rather than thin. Slightly under-scoped only in that no optional parameters (e.g. history or date range) are offered.
The tool covers the core read operation fully: used, remaining, and reset date. There are no write or history operations, but those are arguably outside the stated reporting purpose.