Chargebee MCP Servers

The Model Context Protocol (MCP) enables AI clients to connect to external systems through standardized tools and structured context.

In Chargebee, MCP Servers let you securely expose selected capabilities to external AI clients such as Cursor, Claude, ChatGPT, Codex, and other MCP-compatible tools.

Configure MCP servers from Settings > Agentic AI > MCP Servers.

Overview

Each MCP server has:

• Its own MCP URL
• Its own access toggle
• Its own authentication configuration
• Its own toolsets and tools

Chargebee provides MCP servers for common use cases, such as:

Chargebee Knowledge MCP Server

Lets AI clients answer questions using Chargebee docs and API references.

Most useful when you need to:

• Explain product features
• Answer how-to questions
• Generate integration code snippets using Chargebee APIs

Data Access MCP Server

Lets AI clients retrieve customer, subscription, invoice, transaction, and other billing data from your Chargebee site.

Most useful when you need to:

• Retrieve customer details
• Inspect subscriptions, invoices, and transactions
• Look up payment intents, credit notes, and events
• Support troubleshooting and operational workflows

Onboarding MCP Server

Lets AI clients assist with product catalog setup and onboarding tasks. This MCP server is available only in sandbox sites.

Most useful when you need to:

• Create product catalog
• Manage pricing setup
• Generate demo data

Server URLs

Each MCP server is exposed at a dedicated endpoint on your Chargebee site.

Example pattern: Knowledge MCP Server

US Datacenter - https://<your-site-id>.mcp.chargebee.com/<server-name>

EU Datacenter - https://<your-site-id>.mcp.eu.chargebee.com/<server-name>

AU Datacenter - https://<your-site-id>.mcp.au.chargebee.com/<server-name>

Manage server access

You can manage MCP servers from Settings > Agentic AI > MCP Servers to configure its access and authentication.

Each server has an MCP Access toggle. When enabled, external AI clients can connect to that server using its MCP URL.

Authentication methods

Depending on the server, Chargebee supports one or both of the following authentication methods.

API Key

The API Key method grants full access to all enabled tools in the server and is best suited for:

• Server-to-server integrations
• Internal automations
• Trusted development environments

Clients authenticate by sending the API key in request headers:

Authorization: Bearer <your-api-key>

Admins can generate API key from the server's Authentication section.

OAuth

The OAuth method provides user-based access. Tool access is limited by the signed-in user's role in Chargebee.

This is best suited for:

• User-facing AI clients
• Shared developer tools
• Integrations where access should reflect the end user's permissions

For OAuth-enabled servers, admins can generate client credentials and choose which AI clients those credentials are intended for, such as Claude, Codex, Claude Code, ChatGPT, or other compatible clients.

How tool access works

Tool access depends on both server configuration and authentication method:

• API Key: All enabled tools in the MCP server are accessible
• OAuth: Users can access only the tools their role allows

If both authentication methods are enabled, the effective access depends on the method used by the client.

Toolsets and tools

Each MCP server provides one or more toolsets, where each toolset is a collection of related tools designed for use by external AI clients.

Admins can enable or disable toolsets, and review the tools available in each toolset.

Example: Knowledge MCP Server toolset

The Product Knowledge toolset includes tools such as:

• Explain Chargebee Docs
• Generate Code Samples

Example: Data Access MCP Server toolsets

The Data Access MCP Server exposes multiple toolsets, not limited to the ones listed below:

Customer Lookup

• Find customer by ID
• Find customer by email
• Find customer by company

Product Lookup

• List plans
• List addons
• Get item details by ID

Subscription Lookup

• Get subscription data by ID
• Get subscription data by customer ID

Payment Intent Lookup

• Get payment intent

Invoice Lookup

• Get invoice data by ID
• Get invoice data by customer ID
• Get invoice data by subscription ID
• Get invoice PDF link

Credit Note Lookup

• Get credit note data by ID
• Get credit note PDF link

Transaction Lookup

• List transactions by customer
• List transactions by invoice
• Get transaction

Event Lookup

• List events by event type
• Get events by customer ID

Connect an MCP server to an AI client

Each MCP server page includes an MCP Installation section that helps connect the server to supported AI clients.

Cursor

For public servers such as the Knowledge MCP Server:

{
  "mcpServers": {
    "chargebee-knowledge": {
      "url": "https://<your-site>.mcp.chargebee.com/knowledge_base_agent"
    }
  }
}

For authenticated servers such as the Data Access MCP Server using API key authentication:

{
  "mcpServers": {
    "chargebee-data-access": {
      "url": "https://<your-site>.mcp.chargebee.com/data_lookup_agent",
      "headers": {
        "Authorization": "Bearer <your-api-key>"
      }
    }
  }
}

Using OAuth authentication,

{
  "mcpServers": {
    "chargebee-data-access": {
      "url": "https://<your-site>.mcp.chargebee.com/data_lookup_agent",
      "auth": {
        "client_id": "<your-client-id>"
      }
    }
  }
}

Claude Code

Public server example:

claude mcp add --transport http chargebee-knowledge https://<your-site>.mcp.chargebee.com/knowledge_base_agent

API key example:

claude mcp add --transport http chargebee-data-access https://<your-site>.mcp.chargebee.com/data_lookup_agent --header "Authorization: Bearer <your-api-key>"

Security and governance

When enabling MCP servers:

• Enable only the servers and toolsets your organization needs
• Prefer OAuth when access should reflect individual user roles
• Use API keys only for trusted internal systems and automations
• Rotate keys when needed
• Review whether exposed tools can return customer or billing data

Choosing between Copilot and MCP Servers

Use Chargebee Copilot when you want AI assistance directly inside Chargebee application for internal users.

Use MCP Servers when you want external AI clients to securely access Chargebee knowledge or workflows.