Usage And Billing MCP Server
Related Servers
Alternatives to Usage And Billing MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables 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.2511 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables creating, sending, and tracking invoices from MCP clients like Claude, Cursor, or Windsurf, using a hosted endpoint with API token.MIT

ClockNext MCP Serverofficial
AlicenseAqualityBmaintenanceIntegrates usage-based billing into AI coding tools, enabling meter usage, signal verification, and billing management via the ClockNext API.3596 npmMIT- AlicenseBqualityDmaintenanceEnables interaction with the Telnyx API for billing, phone numbers, and messaging.12MIT

Revenium MCP Serverofficial
AlicenseCqualityBmaintenanceConnects AI agents to Revenium for cost tracking, alerting, and usage-based billing, enabling AI assistants to manage costs, set alerts, and handle billing operations.7158 PyPIMIT
Subotiz MCPofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage subscriptions, usage-based billing, payments, refunds, tax compliance, and invoicing to drive revenue growth.1MIT
TDQS
Scored across 18 tools
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.
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.
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.
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.