MCP Public
Sign in
C

Chargebee

Query Chargebee subscriptions and invoices.

·No reviews yet
Repo
Share:

About

Auto-generated

Chargebee is a Model Context Protocol server in the Commerce & Payments category. It lets AI assistants that speak MCP call its tools and read its resources over STDIO.

Example tools

Illustrative tool names — the actual tool set is defined by the server at runtime.

list_resources
Enumerate resources exposed by this MCP
get_resource
Fetch a resource by ID
invoke
Invoke the primary action of this MCP

Screenshots

No screenshots yet.

Frequently Asked Questions

Common questions about Chargebee.

What does the Chargebee MCP do?
The Chargebee MCP allows you to query subscription and invoice data from Chargebee. It integrates Chargebee's billing functionalities directly into an MCP-compatible environment for streamlined access to financial records and customer subscription statuses.
How do I install the Chargebee MCP?
Installation typically involves cloning the repository from GitHub and then configuring it within your chosen MCP client. Specific steps for clients like Claude Desktop, Cursor, or Cline will vary based on their client-specific extension or plugin mechanisms.
Does the Chargebee MCP require an API key?
Yes, the Chargebee MCP requires an API key for authentication. You will need to obtain this key from your Chargebee account and configure it within the MCP client to enable secure access to your Chargebee data.
What are the key capabilities offered by this Chargebee MCP?
This MCP enables querying of Chargebee subscriptions and invoices. It provides direct access to billing and subscription management functionalities, allowing users to retrieve detailed information about customer financial interactions.
Is there a cost associated with using the Chargebee MCP?
The Chargebee MCP itself is provided by the community as open-source software, so there is no direct cost for the MCP. However, usage costs for the underlying Chargebee service depend on your Chargebee subscription plan.
What is a common limitation when using the Chargebee MCP?
A common limitation is that the MCP's current transport is 'stdio', which may restrict its use in environments that do not support standard input/output for communication. This can impact deployment flexibility in certain client setups.

Install Chargebee

Claude Desktop

Add this to claude_desktop_config.json.

{
  "mcpServers": {
    "chargebee": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-chargebee"
      ]
    }
  }
}

Cursor

Add this to ~/.cursor/mcp.json.

{
  "mcpServers": {
    "chargebee": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-chargebee"
      ]
    }
  }
}

VS Code

Add this to your workspace settings.json.

{
  "mcp.servers": {
    "chargebee": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-chargebee"
      ]
    }
  }
}

Reviews

Sign in to leave a review.

No reviews yet. Be the first!

Discussion(0)

Sign in to join the discussion.

No comments yet.