Introducing Chargebee CLI — query billing data, test webhooks, and generate code samples from your terminal.
chargebee docs

How do I fix MCP server connection errors caused by an incorrect regional URL?

Problem Statement

You see backend connection errors when an AI client such as Claude Code or Cursor tries to connect to a Chargebee Model Context Protocol (MCP) server, such as the Chargebee Data Lookup MCP Server.

  • Your Chargebee site is hosted in the EU or AU data center, but your MCP client uses a US regional URL.
  • Connection errors occur after copying an MCP server URL from documentation or another site that uses a different data center.

Solution

Chargebee MCP server URLs are region-specific. An AI client must use the MCP server URL that matches your Chargebee site's data center. Using a URL from another region can cause backend connection errors.

Before you update your AI client, confirm that MCP Access is turned on for the MCP server in Chargebee. For setup details, see Chargebee Data Lookup MCP Server.

The host in the MCP server URL depends on your site's data center. The path is that server's slug. These examples are for the Chargebee Data Lookup MCP Server:

  • US data center: https://YOUR-CHARGEBEE-SUBDOMAIN.mcp.chargebee.com/data_lookup_agent
  • EU data center: https://YOUR-CHARGEBEE-SUBDOMAIN.mcp.eu.chargebee.com/data_lookup_agent
  • AU data center: https://YOUR-CHARGEBEE-SUBDOMAIN.mcp.au.chargebee.com/data_lookup_agent

Replace YOUR-CHARGEBEE-SUBDOMAIN with your Chargebee site subdomain. For any other MCP server, use the MCP Server URL copied from that server. Do not reuse the data_lookup_agent path.

  1. Log in to Chargebee Billing.
  2. Go to Settings > Configure Chargebee > Agentic AI > MCP Servers.
  3. Select the MCP server you are connecting to, such as Chargebee Data Lookup MCP Server.
  4. Open the Access & Authentication tab.
  5. Under MCP Server URL, copy the URL shown for your site.
  1. Update your AI client's MCP configuration to use the copied URL. For example, update the server URL in your client's MCP settings file or reinstall the server using your client's MCP add command with the correct URL.
  2. Restart or reconnect your AI client, then test the MCP server connection again.

The AI client connects to the MCP server, and the backend connection errors stop.

Important notes

  • Always use the MCP Server URL shown in your Chargebee site. Do not reuse a URL from another Chargebee site or data center.
  • The same regional host rule applies to other Chargebee MCP Servers, including the Chargebee Knowledge Base MCP Server, Onboarding MCP Server, and Custom MCP Server. Copy the URL from that server's Access & Authentication tab. Do not reuse another server's path slug.
  • If connection errors continue after you update the URL, confirm that MCP Access is turned on. For a server that requires authentication, confirm that the API key or OAuth client is configured. The Chargebee Knowledge Base MCP Server does not require authentication. See Chargebee Data Lookup MCP Server.