Skip to main content
Glama
AI Admin API MCP Server

AI Admin API MCP Server

Related Servers

Alternatives to AI Admin API MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      An MCP server for unified cost tracking and analysis across AWS, OpenAI, and Anthropic. It enables users to query expenditures, compare costs across providers, and analyze usage trends through natural language.
      10
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for querying OpenAI usage and cost data, including spend summaries, daily breakdowns, month-over-month comparisons, and token usage by model.
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A read-only local MCP server that lets tool-capable models query provider quotas, balances, reset times, and account-pool aggregates from a local OpenCodex dashboard. It also filters by provider and returns timestamps while keeping credentials and tokens out of results.
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server for querying AI usage metrics (exact tokens, cost, latency, errors, productivity) from a local SQLite database, enabling charts and analysis in Claude Code and Cursor.
      -
    • A
      license
      A
      quality
      C
      maintenance
      CloudOps MCP is a read-only Model Context Protocol server that exposes normalized operational infrastructure context (logs, metrics, deployments, health) to AI agents through a small set of typed, bounded tools.
      6
      MIT

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct concern: listing providers, querying usage, querying costs, and querying dashboard bundles. The descriptions make clear boundaries between them, and the dashboard bundle is a combined view rather than overlapping the individual queries.

    Naming Consistency5/5

    All tool names follow the same verb_noun pattern with a consistent 'ai_admin' prefix. The verbs are distinct and appropriately chosen for their actions, and the naming is uniform and predictable.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its purpose. Each tool fulfills a necessary role in the admin/query domain, and the count is neither too thin nor excessive.

    Completeness4/5

    The tools cover the core read-side needs for AI administration: listing providers and querying usage, costs, and dashboards. However, there are no write or management operations (e.g., enabling/disabling providers), which could be considered a gap for a full admin API, though it's acceptable for a monitoring-focused server.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues