C

chargebee.com

6 integrations · MCP · REST

Chargebee exposes tenant-scoped REST APIs at `/api/v1` and `/api/v2` authenticated with a site API key via HTTP Basic Auth, plus MCP servers for Knowledge Base (public), Data Lookup, Onboarding, and Custom tools authenticated either by per-server Bearer API keys or Chargebee-issued OAuth clients.

discovered 2mo ago
MCP servers4
REST · OpenAPI2
Credentials
Chargebee site API keybasicGet credentials ↗

Log in to the Chargebee application, then go to Settings > Configure Chargebee > API Keys and Webhooks. Open the API Keys tab, click Add an API Key, choose a Full-Access Key, name it, and copy the key. Use the API key for the specific test or live site you are integrating with; keys are environment-specific.

Chargebee MCP server API keybearerGet token ↗

In Chargebee Billing, go to Settings > Configure Chargebee > Agentic AI > MCP Servers, open the specific MCP server, then under Access & Authentication enable MCP Access and create an API key for that server. Chargebee allows up to 5 API keys per MCP server. Use the key as Authorization: Bearer <key>.

Chargebee MCP OAuth clientoauth2Set up OAuth ↗

In Chargebee Billing, go to Settings > Configure Chargebee > Agentic AI > MCP Servers, open the specific MCP server, then under Access & Authentication enable MCP Access and create an OAuth client for the MCP client you want to use. Reuse the same OAuth client ID for users of the same MCP client as Chargebee recommends. Users authenticate through the Chargebee Billing login page and are redirected back to the MCP client. OAuth is not supported on sites with Multi-Business Entity enabled.

conventions · 1/7 published

Publish these signals → /publishing