No user-submitted related servers found.
Scored across 108 tools
Most tools target a distinct resource and action, and the descriptions clearly explain whether they operate on products, subscriptions, invoices, or customers. However, with 108 tools, some clusters (e.g., list_invoices vs get_customer_invoices vs get_subscription_invoices, or charge_invoice vs charge_invoice_external) require careful reading of descriptions to avoid misselection.
The overall verb_noun snake_case pattern is common and readable, but there are notable inconsistencies: remove_ is mixed with delete_, get_ is used for some list endpoints (get_customer_invoices, get_subscription_external_invoices), and unlink_ is used instead of delete_ for external products. The product/subscription rate plan families are named consistently, but the mixed deletion verbs and get/list overlap prevent a higher score.
With 108 tools, the server is massively oversized for an MCP surface. Even if the underlying API is broad, exposing this many tools creates significant cognitive load and selection risk for an agent, far exceeding the 25+ threshold considered too many.
The tool set covers the core recurring-billing lifecycle very well: customers, products, rate plans, charges, subscriptions, invoices, transactions, gateways, currencies, shipping, integrations, and filters all have CRUD or corresponding operations. Minor gaps exist, such as no explicit create_bill_run or a dedicated list_subscription_rate_plan_charges endpoint, but agents can generally work around these via existing includes and related tools.