Skip to main content
Glama
MSPbotsAI

chargebee-mcp

by MSPbotsAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to chargebee-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-server-billing

      santimentasti
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server providing guarded access to a B2B SaaS billing database (customers, subscriptions, invoices, credit notes) and live ECB exchange rates, with read-only tools and one capped, idempotent write for issuing credit notes.
      -

    • askell-mcp

      Neschadin
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Askell's payment and subscription API, allowing users to discover API operations, make raw API calls with approval for mutations, and analyze customers, contracts, billing runs, and webhooks.
      717 npm
      1
      MIT

    • sherweb-mcp

      WYRE-AI
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Sherweb Partner API - distributor billing, service provider management, customer subscriptions, and payable charges
      12
      Apache 2.0

    • datagate-mcp

      hyamie
      A
      license
      B
      quality
      C
      maintenance
      MCP server for the DataGate billing platform API, providing read-only tools to manage customers, invoices, products, agreements, sites, and payments.
      13
      MIT
    • BillingServ MCP by BillingServ

      BillingServ MCPofficial

      BillingServ
      A
      license
      A
      quality
      B
      maintenance
      This is an MCP server for the BillingServ API. Once it's set up, your AI assistant can look up customers, invoices, orders, packages, and reports straight from your BillingServ installation
      3
      115 npm
      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.1/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: customer CRUD, customer contacts, subscription list/retrieve/cancel, invoice list, and transaction list. There is no overlap or ambiguity between tool purposes.

    Naming Consistency5/5

    All tools follow a consistent 'chargebee_verb_noun' pattern with snake_case (e.g., chargebee_list_customers, chargebee_retrieve_subscription). The naming is uniform and predictable across the entire set.

    Tool Count5/5

    With 10 tools, the server is well-scoped for a billing-focused API. Each tool covers a meaningful operation without excessive fragmentation or unnecessary bloat.

    Completeness3/5

    The tool set thoroughly covers customer management and read operations for subscriptions, invoices, and transactions. However, it lacks subscription creation/update and invoice-level actions, which are notable gaps for a billing server's lifecycle.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources