kiro-usage-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KIRO_CLI_PATH | No | Path to the kiro-cli executable, needed if kiro-cli is not on the PATH of the process that starts the server |
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_kiro_usageA | Returns the Kiro plan credits used, remaining and the reset date, read from kiro-cli /usage. |
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
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.