Chargebee for billing and subscriptions
Chargebee is a recurring-billing engine, and its official MCP server exposes the subscription primitives directly: customers, plans, items, prices, invoices, and subscriptions. It is our second pick for billing and subscriptions because that surface is purpose-built for the lifecycle questions this job is full of, why a subscription lapsed, which plan a customer is on, what they were charged.
The server leans into lookups and reasoning over subscription state. An agent can find a customer, trace their plan and price, and pull the subscription record behind a billing question. For developer-first payments where the whole money flow lives in one platform, Stripe ranks ahead, but Chargebee's catalog model is the closer fit when recurring revenue is the center of gravity.
How Chargebee fits
The tools are built for navigating a billing catalog. Find customer by ID, Find customers by email, Find customers by company name, and List customers locate the account; Find plan by name, Find addon by name, Find item by ID, Find item price by ID, and Find item prices by item ID walk the product catalog from plan down to price; and Find subscription by ID pulls the subscription itself. Fields lookup and Filters lookup let the agent discover the queryable fields and filters first, so it builds valid lookups instead of guessing at the schema.
The honest limit is that this surface is read and lookup oriented. The tools listed retrieve and search records rather than mutate them, so the agent reasons about subscription state well but does not, through these tools, push a plan change or issue a refund. Stripe, our top pick, covers a broader payments flow and is the developer-first default; Paddle handles merchant-of-record billing with tax baked in; Polar suits indie and open-source monetization. Reach for Chargebee when the question is about a complex subscription and you want an agent that can trace the catalog and lifecycle accurately.
Tools you would use
| Tool | What it does |
|---|---|
| Fields lookup | Discover the queryable fields available on Chargebee resources so the agent can build valid lookups. |
| Filters lookup | Discover the filters available for narrowing Chargebee resource queries. |
| Find customer by ID | Look up a single customer by their Chargebee customer ID. |
| Find customers by email | Find customers matching an email address. |
| Find customers by company name | Find customers matching a company name. |
| List customers | List customers on the account with filtering and pagination. |
| Find plan by name | Find a plan (item) by its name. |
| Find addon by name | Find an addon (item) by its name. |
| Find item by ID | Look up a product catalog item by ID. |
| Find item price by ID | Look up an item price by ID. |
FAQ
- Can Chargebee's MCP server change a subscription or issue a refund?
- The tools listed here are lookup-oriented: finding customers, plans, items, prices, and subscriptions, plus Fields lookup and Filters lookup to build valid queries. They let an agent read and reason about subscription state rather than mutate it. For a broad payments flow, Stripe is our top pick.
- Why pick Chargebee over Stripe for subscriptions?
- Chargebee's model is catalog-first: plans, addons, items, and item prices map directly to recurring-billing structure, so an agent navigating complex subscription state has the right primitives. Stripe ranks first overall as the developer-first payments default, but Chargebee fits when recurring revenue is the whole point.