Skip to main content
Glama
BrennanWebb

KiroStats

by BrennanWebb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to KiroStats

No user-submitted related servers found.

    Related Servers

    • claudeusage-mcp

      Orellius-Archive
      A
      license
      A
      quality
      Not graded
      maintenance
      Provides 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
      -

    • workflow-hints

      PradellaNicolas
      F
      license
      B
      quality
      C
      maintenance
      Enables Cursor users to track local workflow state and receive contextual nudges, daily summaries, and Windows toast notifications for sessions, edits, MCP usage, and plans.
      5
      -

    • mcp-token-saver

      Talap-creator
      A
      license
      A
      quality
      C
      maintenance
      Real-time Claude.ai subscription awareness for AI coding assistants. Surfaces live utilization, forecasts limits, gates expensive operations, and measures real per-task cost.
      5
      17 npm
      6
      MIT

    • Cursor Pro Limits MCP Server

      mehmetfiskindal
      A
      license
      B
      quality
      D
      maintenance
      Enables real-time monitoring of Cursor Pro usage limits and API quotas across different AI services. Tracks Sonnet 4.5, Gemini, and GPT-5 request usage with alerts when approaching subscription limits.
      6
      2 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    All tools have distinct purposes: plan-level usage, session metrics, session summary, interaction logging, and session initiation. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case (get_plan_usage, get_session_stats, get_session_summary, log_interaction, start_session). No deviations.

    Tool Count5/5

    5 tools is well-scoped for a session and usage tracking server. Each tool serves a clear need without redundancy or gaps.

    Completeness5/5

    Covers the full lifecycle: session start, per-turn logging, current stats, formatted summary, and plan-level usage. No obvious missing operations for the intended domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources