Skip to main content
Glama
myapitaco

Apitaco MCP Server

Official
by myapitaco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Apitaco MCP Server

No user-submitted related servers found.

    Related Servers

    • Claude Code Usage

      wheelbarrel00
      A
      license
      Not graded
      quality
      C
      maintenance
      Surface Claude Code token usage, estimated cost, and plan-limit status in any MCP client. Enables agents to query usage data from local logs and Anthropic API.
      MIT

    • claude-usage

      drmuzikbpn
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code sessions to check account rate-limit headroom, local token spend, and live session status, with read-only MCP tools for limits, summaries, token usage, and session listing.
      2
      MIT

    • Cognitally

      kamanager2012
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents such as Claude Code, Cursor, Codex, and OpenCode to query local token usage, costs, quotas, projects, and models through six strictly read-only tools. All data stays on the local machine, drawn from passively parsed session logs rather than uploaded telemetry.
      MIT

    • patch-usage-mcp

      hkfe
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to read your Patch API budget usage, including spend, burn rate, and account details, directly from chat.
      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/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: balance, usage stats, and available models. There is no overlap in purpose, and an agent can easily select the correct tool based on the user's request.

    Naming Consistency5/5

    All tools follow a consistent pattern: apitaco_ prefix plus a clear verb_noun structure (get_balance, get_usage, list_models). The convention is predictable and readable.

    Tool Count5/5

    Three tools is appropriate for a focused account-information server. Each tool earns its place by covering a distinct read-only query without unnecessary surface area.

    Completeness4/5

    The surface covers the core account queries: balance, usage, and model pricing. Minor gaps like detailed historical usage breakdowns or account settings exist, but agents can work around them for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources