KiroStats
KiroStats is a real-time credit usage and session tracking MCP server for Kiro IDE that reads directly from local execution files. It provides the following capabilities:
start_session: Initialize a new chat session, capturing a snapshot of current credits and time as a baseline for delta calculations.log_interaction: Record individual agent turns within a session, including optional thinking/processing time (thinking_seconds), to maintain cumulative metrics.get_session_stats: Retrieve live session metrics including credits consumed (delta from session start), cumulative agent thinking time (total_thinking_time), total wall-clock duration (wall_clock_time), and interaction count.get_plan_usage: View full billing-cycle plan data including credit limit, total credits used, remaining credits, overage details, and billing reset date.get_session_summary: Generate a pre-formatted session summary suitable for pasting into tools like Jira comments or PR descriptions.
Provides session summaries formatted for Jira tickets, allowing users to paste or auto-attach credit usage, thinking time, and other session metrics to issues.
Click on "Install 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., "@KiroStatsWhat's my credit usage this session?"
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.
KiroStats
Real-time credit usage and session tracking for Kiro IDE — as an MCP server.
No auth. No network. No cloud dependency. Reads directly from Kiro's local execution files.
What You Get
Three metrics, live from the same source that powers Kiro's "Est. Credits Used" display:
Credits Used — exact per-turn credits from execution files
Agent Time — cumulative time Kiro spent processing
Session Time — total time since the chat started
Related MCP server: Cursor Pro Limits MCP Server
Usage
Type /stats in any Kiro chat.
How It Works
Kiro persists every agent execution to disk as JSON files containing usageSummary[] arrays with exact per-turn credit values. KiroStats reads these files directly.
Data source:
%APPDATA%/Kiro/User/globalStorage/kiro.kiroagent/{workspace-hash}/{session-hash}/{execution-hash}The single tool (get_session_stats) finds the running execution, groups all executions by chatSessionId, and returns aggregated credits and timing.
Install
git clone https://github.com/BrennanWebb/KiroStats.git
cd KiroStats
.\install.ps1The installer:
Pip-installs the MCP server package
Registers it in
~/.kiro/settings/mcp.jsonCreates a
/statssteering file for manual invocation
Restart Kiro after install.
Manual Install
pip install -e .Add to ~/.kiro/settings/mcp.json:
{
"mcpServers": {
"kiro-stats": {
"command": "kiro-stats-mcp",
"autoApprove": ["get_session_stats"]
}
}
}Copy .kiro/steering/stats.md from this repo to ~/.kiro/steering/.
Tool
Tool | Returns |
|
|
Supported Platforms
OS | Kiro Data Path |
Windows |
|
macOS |
|
Linux |
|
Requirements
Python 3.10+
Kiro IDE installed and opened at least once
Uninstall
pip uninstall kiro-stats-mcp
# Remove "kiro-stats" from ~/.kiro/settings/mcp.json
# Delete ~/.kiro/steering/stats.mdLicense
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/BrennanWebb/KiroStats'
If you have feedback or need assistance with the MCP directory API, please join our Discord server