Skip to main content
Glama
Ludoonus

agentops-mcp

by Ludoonus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to agentops-mcp

No user-submitted related servers found.

    Related Servers

    • rybbit-mcp

      nks-hub
      A
      license
      A
      quality
      B
      maintenance
      Enables querying Rybbit Analytics data directly through MCP-compatible clients like Claude Code. It provides tools for monitoring website statistics, user sessions, error logs, funnels, and performance metrics via natural language.
      40
      13 npm
      4
      MIT

    • Cloud FinOps Analyst MCP

      mihirkadam19
      A
      license
      A
      quality
      C
      maintenance
      Enables analyzing AWS cloud costs through natural language queries, providing cost summaries, anomaly detection, idle resource identification, rightsizing recommendations, and tagging compliance via Claude.
      10
      25 npm
      MIT

    • Claude Stats MCP

      upJiang
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides statistical analysis and usage tracking for Claude Code, enabling users to query daily/monthly stats, compare users, analyze trends, detect anomalies, and generate usage reports through natural language.
      1
      -

    • Claude Telemetry MCP

      cordlesssteve
      F
      license
      B
      quality
      Not graded
      maintenance
      Provides comprehensive telemetry and usage analytics for Claude Code sessions, including token usage tracking, cost monitoring, and tool usage patterns. Enables users to monitor their Claude usage with detailed metrics, warnings, and trend analysis.
      12
      -
    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

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a clearly distinct aspect of agent operations: actions, costs, efficiency, and safety. No overlap or ambiguity exists between the tool purposes.

    Naming Consistency5/5

    All tool names follow a consistent adjective_noun pattern using underscores, making them predictable and easy to understand (e.g., audit_summary, cost_summary).

    Tool Count5/5

    With only 4 tools, the server is tightly scoped around monitoring agent behavior. Each tool earns its place, and the count is appropriate for a focused observability server.

    Completeness5/5

    The tool surface covers the essential dimensions of agent operations: actions, costs, efficiency, and safety. There are no obvious gaps for the intended purpose of auditing and optimizing agent performance.

    Maintenance

    ActivitySlowing
    ResponsivenessSyncing

    Resources