chargebee-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@chargebee-mcp What are our active subscriptions?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
chargebee-mcp
Chargebee MCP Service — a stateless HTTP MCP server wrapping the Chargebee REST API v2 for account/customer management use cases (company records, personnel/contacts, subscription lookups, and financial reporting lookups).
Tech stack: Python 3.12 + uv + FastMCP (Starlette/Uvicorn)
MSPbots Connector
The MCP Gateway built for MSPs: visible, controlled, and your data stays where it belongs.
Get started at connect.mspbots.ai →
MSPbots Connector gives your AI clients one MCP URL to reach your entire MSP stack (RMM, PSA, documentation, security, finance), and gives you control over who can call which tool and a record of everything that was called.
Hosted service: connect.mspbots.ai · Free to use.
Why Connector

Visible | Every tool call is logged: who, which vendor, when. Usage dashboard, CSV export, SIEM streaming. |
Controlled | Role-based, per-tool allowlist. Deny by default. |
Protected | Credentials encrypted per record. AI clients never see your vendor passwords or tokens. |
MSP-native | Built for the MSP stack only: RMM, PSA, documentation, security, finance. |
Quick start
Sign up at connect.mspbots.ai.
Connect your vendors. Pick from 150+ connectors and authorize each one on the vendor's own page, or bring your own API keys. No extra vendor accounts needed.
Set access. Create roles and decide which tools each role may call. Nothing is allowed until you allow it.
Add your MCP URL to your AI client. Copy the URL from your Connector dashboard into Claude, ChatGPT, Cursor, VS Code, Gemini, Codex, or any MCP-capable client.
Ask your AI to do real work, and watch every call appear in the audit log.
Features
Unified gateway
One MCP URL for all your AI clients
150+ connectors across the MSP stack
Custom MCP servers supported, free
Authorization happens on each vendor's own page; the AI never sees passwords or tokens
Bring your own credentials: use the vendor API keys you already have
Multiple accounts per app; connect once, reuse across AI clients
Tool search: finds the right action for the task
One sign-in; vendor credentials are injected behind the scenes and OAuth tokens refresh automatically
Visibility
Audit log for every tool call (who, which vendor, when)
Usage dashboard: call volume, top vendors, error rate, per-user activity
Export audit logs to CSV, or stream to Loki, Graylog, or LogScale (SIEM)
Optional recording of tool arguments and result summaries (off by default, enabled per organization)
Control
Per-role, per-tool allowlist, deny by default
owner / admin / member roles
SCIM provisioning with Entra ID, Okta, JumpCloud, and Google Workspace
Security
Credentials encrypted one record at a time (AES-256-GCM, per-record key)
AI clients authenticate with OAuth 2.1 + PKCE
Vendor responses are scanned for prompt-injection patterns and returned as structured data. This is one layer of defense, not a guarantee against every attack.
Static egress IP for customer firewall and API allowlisting
Pricing
Free.
Links: connect.mspbots.ai · mspbots.ai
Related MCP server: sherweb-mcp
When would an agent use this
Chargebee is MSPbots' own subscription billing/revenue platform. An agent should reach for this MCP for requests like:
"Look up this customer's billing account / create a new customer record" →
chargebee_retrieve_customer/chargebee_create_customer"Update this company's billing email or address" →
chargebee_update_customer"Who are the contacts under this account?" →
chargebee_list_customer_contacts"What subscription plan is this customer on, is it active?" →
chargebee_list_subscriptions(filter bycustomer_id) orchargebee_retrieve_subscription"Cancel this customer's subscription" →
chargebee_cancel_subscription"Pull this customer's recent invoices / did this transaction go through?" →
chargebee_list_invoices(what was billed) /chargebee_list_transactions(whether payment settled)
Scope
Chargebee's official MCP Server offering (the "Data Lookup MCP Server") was evaluated first and found unsuitable as a replacement: it is read-only, covers roughly a dozen resource categories, and is missing Coupons, the Item/Item Price/Item Family product-catalog resources, and Upcoming Invoice Estimates entirely — none of which can be added on top of it. This service instead wraps the full Chargebee REST API directly.
Out of Chargebee's ~438 REST API operations across 77 resources, this service started at 30 tools selected for account/company/personnel/report management use cases, then was trimmed down to the 10 core tools below (user-confirmed reduction — dropped delete/merge/payment-role/hierarchy on customers, all contact write ops, subscription create/update/pause/resume/reactivate/term-end/scheduled-changes, all payment-source tools, and invoice-retrieve/credit-notes from reports):
Category | Count | Resources |
Company (Customer) | 4 | create, retrieve, update, list |
Personnel (Customer Contacts) | 1 | list contacts under a customer |
Account (Subscription) | 3 | list, retrieve, cancel |
Report (Invoices/Transactions) | 2 | list invoices, list transactions |
Quick Start
# Install dependencies
cd D:\claude\project\chargebee-mcp
uv sync
# Run in stdio mode (for Claude Desktop)
$env:CHARGEBEE_SITE="your-site"
$env:CHARGEBEE_API_KEY="your_api_key"
uv run chargebee-mcpConfiguration
Copy .env.example to .env and fill in your values:
Variable | Default | Description |
| — | Chargebee site name (the subdomain in |
| — | Chargebee API key |
|
|
|
|
|
|
|
| HTTP server port |
Get your API key: Chargebee Billing → Settings → Configure Chargebee → API Keys and Webhooks → API Keys tab.
HEADER Authentication Parameters
In Gateway mode, every request must carry the following two HTTP Headers:
Header | Type | Required | Default | Allowed values | Description | Example |
| string | Yes | None | None | Chargebee site name (i.e. the subdomain part of |
|
| string | Yes | None | None | Chargebee API Key (generated on the Settings → Configure Chargebee → API Keys and Webhooks page); this service uses it as the HTTP Basic Auth username with the password left empty |
|
Claude Desktop Setup
Add to claude_desktop_config.json:
{
"mcpServers": {
"chargebee": {
"command": "uv",
"args": ["run", "--directory", "D:/claude/project/chargebee-mcp", "chargebee-mcp"],
"env": {
"CHARGEBEE_SITE": "your-site",
"CHARGEBEE_API_KEY": "your_api_key"
}
}
}
}Transport Modes
stdio (Claude Desktop / CLI)
$env:CHARGEBEE_SITE="your-site"
$env:CHARGEBEE_API_KEY="your_api_key"
uv run chargebee-mcpHTTP — single-tenant
$env:CHARGEBEE_SITE="your-site"
$env:CHARGEBEE_API_KEY="your_api_key"
$env:MCP_TRANSPORT="http"
$env:AUTH_MODE="env"
uv run chargebee-mcpHTTP — gateway / multi-tenant
$env:MCP_TRANSPORT="http"
$env:AUTH_MODE="gateway"
uv run chargebee-mcp
# Each request must include: X-Chargebee-Site and X-Chargebee-Api-Key headersAvailable Tools (10)
Company (Customer) — 4
Tool | Description | Parameters |
| List customers (companies) |
|
| Create a customer (company) |
|
| Retrieve a customer by ID |
|
| Update a customer |
|
Personnel (Customer Contacts) — 1
Tool | Description | Parameters |
| List contacts under a customer |
|
Account (Subscription) — 3
Tool | Description | Parameters |
| List subscriptions |
|
| Retrieve a subscription by ID |
|
| Cancel a subscription |
|
Report (Invoices / Transactions) — 2
Tool | Description | Parameters |
| List invoices |
|
| List payment/refund transactions |
|
Filter parameters
Chargebee's list endpoints use compound filter query keys with an operator suffix, e.g. email[is]=a@b.com, created_at[after]=1700000000, status[in]=["active","paused"]. Rather than expanding every field × operator combination into separate function parameters, list tools accept an optional filters: dict[str, str] argument — pass the literal Chargebee query key (including the [operator] suffix) as the dict key. Supported fields per resource are documented in each tool's docstring; supported operators are [is], [is_not], [starts_with], [in], [not_in], [between], [after], [before], [on], [none], [is_present] (availability varies by field type — see Chargebee's filter documentation).
Request encoding
Chargebee's REST API uses application/x-www-form-urlencoded request bodies, not JSON. Nested object parameters (billing_address, meta_data) are accepted as plain Python dict and flattened server-side into Chargebee's bracket-notation form fields (billing_address[line1]=...) — see _flatten_form() in api_client.py. _flatten_form() also supports flattening lists and "array of hashes" fields (Chargebee's field[subfield][index]=value convention), but none of the current 10 tools take such a parameter — that code path is currently unexercised.
Known Gaps
Verified against a live Chargebee account. Using a real production API key + site:
chargebee_list_customers,chargebee_retrieve_customer,chargebee_list_customer_contacts,chargebee_list_subscriptions,chargebee_list_invoices, andchargebee_list_transactionsall returned real data (200) through the running service. Gateway 401 gating was re-confirmed with a fresh MCP session + an invalid API key (correctly rejected by Chargebee withapi_authentication_invalid_key).Write operations (
chargebee_create_customer,chargebee_update_customer,chargebee_cancel_subscription) have not been exercised end-to-end — only verified structurally (schema, request construction). This was a deliberate choice during self-test: the only available credentials are for MSPbots' own live production Chargebee site, and mutating real billing/subscription data to self-test was avoided. If write-path verification is needed, test against a Chargebee test site (not a live/production API key).Nested fields (
billing_address,meta_data) are accepted as genericdictrather than fully-typed sub-schemas — callers must know Chargebee's field names for these substructures (documented in each tool's docstring where practical, otherwise see the Chargebee API reference).List-endpoint filters are not expanded into named parameters (see "Filter parameters" above) — this keeps the tool count/signature size manageable but pushes filter-key correctness onto the caller.
Scope is limited to the 10 operations above (company/personnel/account/report management, user-trimmed down from an initial 30). Everything else — Coupons, Items/Item Prices/Item Families, Estimates, Orders, Payment Sources, Credit Notes, subscription create/update/pause/resume/reactivate, customer delete/merge/hierarchy, contact write ops, etc. — is out of scope per user-confirmed selection.
API Reference
Chargebee OpenAPI Specification (
chargebee_api_v2_pc_v2_spec.json— API v2 + Product Catalog v2, used as the source of truth for this service)Chargebee Official MCP Servers (evaluated and found insufficient — see Scope above)
Available Tools
10 toolschargebee_cancel_subscriptionA
Cancel a subscription (account).
API: POST /subscriptions/{subscription-id}/cancel_for_items
Args:
subscription_id: The subscription's unique ID.
cancel_option: "immediately", "end_of_term", or "specific_date".
end_of_term: Shorthand for cancel_option="end_of_term" (legacy field, kept for compatibility).
cancel_at: Unix timestamp (seconds) — required when cancel_option="specific_date".
cancel_reason_code: A reason code configured in your Chargebee site for this cancellation.
credit_option_for_current_term_charges: "prorate", "full", or "none" —
how to credit unused charges for the current term.
unbilled_charges_option: "invoice", "delete", or "carry_forward" — how
to handle unbilled usage charges.
Inputs: subscription_id (required), cancel_at, end_of_term, cancel_option, +3 more. Returns: result
chargebee_create_customerA
Create a customer (company).
API: POST /customers
Args:
first_name: Customer's first name.
last_name: Customer's last name.
email: Customer's email address.
company: Company name.
phone: Phone number.
id: Optional custom customer ID (auto-generated if omitted).
auto_collection: "on" or "off" — whether invoices are auto-collected.
taxability: "taxable" or "exempt".
locale: Customer's locale (e.g. "en", "fr-CA").
meta_data: Arbitrary key-value metadata dict.
billing_address: Billing address fields, e.g. {"line1": "...",
"city": "...", "state": "...", "zip": "...", "country": "US"}.
Inputs: id, email, phone, locale, +7 more. Returns: result
chargebee_list_customer_contactsA
List the contacts (personnel) associated with a customer (company).
API: GET /customers/{customer-id}/contacts
Args:
customer_id: The customer's unique ID.
limit: Max results per page (1-100, default 10).
offset: Pagination cursor from a previous response's next_offset.
Inputs: customer_id (required), limit, offset. Returns: result
chargebee_list_customersA
List customers (companies).
API: GET /customers
Args:
limit: Max results per page (1-100, default 10).
offset: Pagination cursor from a previous response's next_offset.
include_deleted: Include deleted customers in the results.
filters: Optional Chargebee compound filter fields, passed through
as literal query keys, e.g. {"email[is]": "a@b.com",
"company[is]": "Acme", "created_at[after]": "1700000000"}.
Supported fields: id, first_name, last_name, email, company,
phone, auto_collection, taxability, created_at, updated_at,
offline_payment_method, auto_close_invoices, channel,
business_entity_id, relationship. Supported operators vary by
field type: [is], [is_not], [starts_with], [in], [not_in],
[between], [after], [before], [on], [none], [is_present].
Inputs: limit, offset, filters, include_deleted. Returns: result
chargebee_list_invoicesA
List invoices.
API: GET /invoices
Args:
limit: Max results per page (1-100, default 10).
offset: Pagination cursor from a previous response's next_offset.
include_deleted: Include deleted invoices in the results.
filters: Optional Chargebee compound filter fields, passed through
as literal query keys, e.g. {"customer_id[is]": "cus123",
"status[in]": "[\"paid\",\"payment_due\"]",
"date[after]": "1700000000"}. Supported fields: id,
subscription_id, customer_id, recurring, status, price_type,
date, paid_at, total, amount_paid, amount_adjusted,
credits_applied, amount_due, dunning_status, payment_owner,
updated_at, channel, voided_at, void_reason_code, exclude,
einvoice. Supported operators vary by field type: [is],
[is_not], [in], [not_in], [between], [after], [before], [on],
[none], [is_present].
Inputs: limit, offset, filters, include_deleted. Returns: result
chargebee_list_subscriptionsA
List subscriptions (accounts).
API: GET /subscriptions
Args:
limit: Max results per page (1-100, default 10).
offset: Pagination cursor from a previous response's next_offset.
include_deleted: Include deleted subscriptions in the results.
filters: Optional Chargebee compound filter fields, passed through
as literal query keys, e.g. {"customer_id[is]": "cus123",
"status[in]": "[\"active\",\"non_renewing\"]"}. Supported
fields: id, customer_id, item_id, item_price_id, status,
cancel_reason, cancel_reason_code, remaining_billing_cycles,
created_at, activated_at, next_billing_at, cancelled_at,
has_scheduled_changes, updated_at, offline_payment_method,
auto_close_invoices, override_relationship,
business_entity_id, channel, decommissioned. Supported
operators vary by field type: [is], [is_not], [in], [not_in],
[between], [after], [before], [on], [none], [is_present].
Inputs: limit, offset, filters, include_deleted. Returns: result
chargebee_list_transactionsA
List payment/refund transactions.
API: GET /transactions
Args:
limit: Max results per page (1-100, default 10).
offset: Pagination cursor from a previous response's next_offset.
include_deleted: Include deleted transactions in the results.
filters: Optional Chargebee compound filter fields, passed through
as literal query keys, e.g. {"customer_id[is]": "cus123",
"type[is]": "payment", "date[after]": "1700000000"}. Supported
fields: id, customer_id, subscription_id, payment_source_id,
payment_method, gateway, gateway_account_id, id_at_gateway,
reference_number, type, date, amount, amount_capturable,
status, updated_at. Supported operators vary by field type:
[is], [is_not], [in], [not_in], [between], [after], [before],
[on], [none], [is_present].
Inputs: limit, offset, filters, include_deleted. Returns: result
chargebee_retrieve_customerA
Retrieve a customer (company) by ID.
API: GET /customers/{customer-id}
Args:
customer_id: The customer's unique ID.
Inputs: customer_id (required). Returns: result
chargebee_retrieve_subscriptionA
Retrieve a subscription (account) by ID.
API: GET /subscriptions/{subscription-id}
Args:
subscription_id: The subscription's unique ID.
Inputs: subscription_id (required). Returns: result
chargebee_update_customerA
Update a customer (company).
API: POST /customers/{customer-id}
Args:
customer_id: The customer's unique ID.
first_name: Customer's first name.
last_name: Customer's last name.
email: Customer's email address.
company: Company name.
phone: Phone number.
auto_collection: "on" or "off".
taxability: "taxable" or "exempt".
locale: Customer's locale.
invoice_notes: Default notes shown on the customer's invoices.
meta_data: Arbitrary key-value metadata dict.
Inputs: customer_id (required), email, phone, locale, +7 more. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
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.
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.
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.
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
Related MCP Connectors
Unofficial Chargebee MCP Pack — wraps the Chargebee API v2
MCP server for Recurly — accounts, subscriptions, invoices, plans; cancel & pause subs.
MCP server for Autumn — read customers, plans, balances & invoices; track usage and attach plans.
Related MCP Servers
AlicenseAqualityFmaintenanceMCP Server that connects AI agents to Chargebee Platform.269 npm16MIT- AlicenseAqualityBmaintenanceMCP server for Sherweb Partner API - distributor billing, service provider management, customer subscriptions, and payable charges12Apache 2.0
- AlicenseBqualityCmaintenanceMCP server for the DataGate billing platform API, providing read-only tools to manage customers, invoices, products, agreements, sites, and payments.1324 PyPIMIT

BillingServ MCPofficial
AlicenseAqualityCmaintenanceThis 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 installation3115 npmMIT