Provider REST API

14 actions

Connect Claude to Chargebee

Read and manage customers, subscriptions, invoices, transactions and the product catalog. Toolspoke puts 14 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connect View pricing

Connection: Provider REST API
Authentication: API key
Actions exposed: 14
What a call bills: Nothing
Adapter: Maintained by Toolspoke

Connected in three steps

1
Install Chargebee
Open the marketplace in your workspace, add Chargebee to the project your agents work in, and it appears on the gateway immediately.
2
Connect the credential
Authenticate with api key. Where to get one, and what it has to be able to reach, is the next section.
3
Point your agent at the gateway
Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.

.mcp.json

{
  "mcpServers": {
    "toolspoke": {
      "type": "http",
      "url": "https://toolspoke.com/mcp"
    }
  }
}

One block covers every tool you have installed. Chargebee shows up in the client as soon as your policy allows it, and so does everything else you install later.

Where the address goes, per client

Claude Code: Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcp
Claude and Claude Desktop: Settings, then Connectors, then Add custom connector
https://toolspoke.com/mcp
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json for one project
{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }
Codex: ~/.codex/config.toml
[mcp_servers.toolspoke] url = "https://toolspoke.com/mcp"
VS Code: .vscode/mcp.json, or the MCP: Add Server command
{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

What Chargebee asks for

API key. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

Site nameRequired: Just the subdomain. For https://acme.chargebee.com this is acme; a test site is usually acme-test.; acme
API key, then a colonRequired: Chargebee → Settings → Configure Chargebee → API Keys and Webhooks → API Keys → Add an API Key. Paste the key followed by a single colon (key:) - Chargebee reads it as the HTTP Basic username with an empty password. A Read-only: All key covers every read here; create_customer, update_customer, cancel_subscription and refund_invoice need a Full-Access key. Test and live sites have different keys.; live_AbC123…:

What Claude can do in Chargebee

14 actions, each one declared and named by the connector rather than discovered at runtime. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.

Reads: 10Reads
Writes: 2Writes
Destructive: 2Destructive

Reads

Fetches data and changes nothing.

list_customers
List customers, newest first, optionally only one email address. Chargebee wraps each row as {customer: {...}} inside list, and returns next_offset only when there is another page - pass it back as offset.
get_customer
Retrieve one customer by id, with billing address, payment method summary and balances.
list_subscriptions
List subscriptions, optionally by status or customer. Each row carries the plan item prices, billing period, next billing date and MRR.
get_subscription
Retrieve one subscription by id, together with its customer and card on file.
list_invoices
List invoices, optionally by status, customer or subscription. Amounts are in the currency's minor unit (cents).
get_invoice
Retrieve one invoice by id, with its line items, taxes, payments and billing address.
list_transactions
List payment transactions - payments, refunds and reversals - optionally by customer, status or type.
list_item_prices
List item prices - the plans, add-ons and charges subscriptions are built from - with their amounts, periods and currencies.
list_credit_notes
List credit notes, optionally by customer, status or the invoice they reference.
list_events
List site events - subscription_created, payment_succeeded, invoice_generated and the rest - newest first. Each event carries a full copy of the records it touched, so this is the audit trail of what changed and when. occurred_after is a Unix timestamp in seconds.

Writes

Creates or updates something on the other side.

create_customer
Create a customer. A write rather than destructive: it charges nothing and starts no subscription. id is optional - Chargebee generates one when it is left out.
update_customer
Update a customer's name, email, company, phone or auto-collection setting. Billing address and VAT number are changed through a separate Chargebee call this connector does not expose.

Destructive

Deletes or permanently alters something. Worth granting on purpose.

cancel_subscription
Cancel a subscription (Product Catalog 2.0). Destructive because it stops billing a paying customer and, with cancel_option immediately, ends their access now; a cancelled subscription has to be reactivated deliberately. end_of_term lets the paid period run out first.
refund_invoice
Refund a paid invoice to the customer's original payment method, in full or in part, and create a credit note for it. Destructive because it moves money out of the business and cannot be undone. refund_amount is in the currency's minor unit (cents); leave it out to refund the whole invoice.

What it will not do

Enforced by the gateway rather than left to convention, which is why each of these can be stated flatly.

It cannot call anything else: The 14 actions above are the whole of it. A call to any other name is refused before it reaches Chargebee rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
It reaches no further than your credential: Toolspoke holds no access to Chargebee of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
It never hears from Chargebee: Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Chargebee. An agent has to ask.
It does not smooth over provider limits: Toolspoke does not retry, queue or back off around Chargebee's own rate limits. A call that Chargebee refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in Chargebee?

14 named actions: 10 that only read, 2 that write and 2 that delete or permanently alter something. They include list_customers, get_customer and create_customer. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.

What credentials does the Chargebee connector need?

API key. The connector asks for site name and api key, then a colon. Values are encrypted at rest and attached to the outbound request by the gateway, so they are never part of the arguments an agent sends and never reach the audit log.

Does the Chargebee connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 14 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.

What does the Chargebee connector not do?

The 14 actions above are the whole of it. A call to any other name is refused before it reaches Chargebee rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. Toolspoke holds no access to Chargebee of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Chargebee. An agent has to ask. Toolspoke does not retry, queue or back off around Chargebee's own rate limits. A call that Chargebee refuses comes back to the agent as a failed call.

Can I limit which actions an agent can call?

Yes, in two places. The project switches Chargebee's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.

What gets recorded when an agent calls Chargebee?

Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and what the call cost in sandbox time and model tokens. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.

More payments connectors

Browse all of them