Skip to main content
Glama
BACH-AI-Tools

Usage And Billing MCP Server

Related Servers

Alternatives to Usage And Billing MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Enables interaction with the Pulse usage-based billing platform to track metering events, manage customers, and generate invoices. It also supports managing products, payment links, and AI agent usage directly through MCP-compatible assistants.
      25
      5 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read and manage an MSP's billing through the partner API, covering customers, invoices, standalone payment requests, transactions, payouts, and webhook subscriptions. Credentials are supplied per request via headers, so it stays stateless and multi-tenant while supporting both sandbox and production environments.
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Exposes three MCP tools that let Claude Desktop, Cursor, Claude Code, and Cline query an account's current balance in USD, retrieve token and cost usage statistics for the last N days, and list supported models with per-million-token pricing. Answers questions like "How much have I spent in the last 30 days?" by calling those tools directly from any MCP-compatible client.
      3
      MIT

    TDQS

    C2.5/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes targeting specific resources like meters, products, plans, and usage, with minimal overlap. However, 'get_account_customer' and 'get_accounts_customers' could cause minor confusion due to similar naming, and 'health_check' is a utility that stands apart from the core billing domain.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern (e.g., create_meter, get_product) with clear CRUD operations, which aids predictability. A minor deviation is 'get_plans_of_a_product' which uses 'of_a' instead of a simpler pattern like 'get_product_plans', slightly breaking the consistency.

    Tool Count4/5

    With 18 tools, the count is reasonable for a billing and usage management domain, covering various entities like products, meters, and accounts. It's slightly on the higher side but well-scoped, as each tool serves a distinct function without appearing bloated.

    Completeness4/5

    The tool set provides comprehensive CRUD coverage for core resources (e.g., products, meters, usage) and includes utility functions like health checks. A minor gap is the lack of update or delete operations for meters, plans, and product items, which might require workarounds but doesn't severely hinder core workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues