Chargebee
Connect Chargebee to manage customers, subscriptions, invoices, credit notes, transactions, coupons, and quotes.
You end up with two values: your Chargebee site name (the part before .chargebee.com) and a full-access API key that starts with live_ or test_.
- Setup time
- 4 min
- Auth
- API credentials
- API base URL
- https://{site}.chargebee.com/api/v2
- Rate limits
- Live sites default to 150 calls a minute on Starter, 1,000 on Performance and 3,500 on Enterprise. Test sites are capped at 150 a minute, and anything over returns HTTP 429.
Before you begin
- A Chargebee Billing site, live or test
- An Admin or Owner user. The API Keys screen is hidden from users without configuration rights
- Decide up front whether you are connecting the live site or the test site. Keys never work across the two
Get your credentials
Sign in and note your site name
Sign in at app.chargebee.com/login and read the address bar. In https://acme.chargebee.com the site name is acme, and that is what PopMCP's Site name field wants.
Open the API keys screen
Go to Settings → Configure Chargebee → API Keys and Webhooks, then click the API Keys tab.
API Keys and Webhooks
Keys and endpoints that let other systems talk to this site.
| Name | Type | Key | Status | Created |
|---|---|---|---|---|
| Checkout pagebrowser only | Publishable | test_****7ab3 | Active | Mar 4, 2026 |
| Data warehousenightly export | Read-Only: All | test_****02e9 | Active | Jan 12, 2026 |
| Old billing scriptretired | Full-Access | test_****55c7 | Disabled | Aug 2, 2025 |
The three-dot menu on a row offers Disable and Delete.
Add a full-access key
Click + Add API Key, select Full-Access Key, name it PopMCP, and click Create Key.
API Keys and Webhooks
Copy the key and paste both values into PopMCP
Copy the key from the dialog and paste it into PopMCP's API key field, then type your site name into Site name.
API Keys and Webhooks
- Site name
- acme
- API key
- live_****9c1d
- Auth
- HTTP Basic, key as username, empty password
Chargebee reveals the full key once, at creation.
Connect in PopMCP
Open your workspace, choose Chargebee in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| Site nametext | Your Chargebee site subdomain: the part before .chargebee.com. You can paste the full URL (https://acme.chargebee.com) too. For a test site use the full name including -test (e.g. acme-test). |
| API keysecret | Chargebee → Settings → Configure Chargebee → API Keys & Webhooks → API Keys → create/copy a Full-Access key. Stored encrypted; used server-side only. A read-only key works too but will reject writes.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Chargebee immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
PopMCP shows the Chargebee connection as Connected and a customer or subscription list tool returns records from your site.
Troubleshooting
401 Unauthorized
Why: The key belongs to the other environment, or it was disabled on the API Keys tab.
Fix: Open API Keys on the exact site you typed into PopMCP and create a new full-access key there.
Requests fail before Chargebee answers, or the host is not found
Why: The Site name field holds the full URL, a trailing slash, or is missing the -test suffix.
Fix: Enter just the subdomain, for example acme or acme-test.
Write tools return an error but reads work
Why: You pasted a read-only key.
Fix: Create a Full-Access Key and reconnect.
You closed the dialog before copying the key
Why: Chargebee shows the full value once and stores only a masked version afterwards.
Fix: Delete that key and add a new one.
429 Too Many Requests
Why: Per-minute request or concurrency limit hit.
Fix: Retry after about a minute, or contact Chargebee support for a higher limit on your plan.