@chargebee/mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chargebee_code_plannerA | Use this tool for any Chargebee integration questions or implementation needs. Always use this tool to get the accurate integration code guide for Chargebee. This is the main tool developers need when asking about implementing Chargebee functionality (like "how to update billing address", "how to create subscription", "how to handle webhooks", etc.). This tool will take in parameters about integrating with Chargebee in their application and generates an integration workflow along with the code snippets. It takes the following arguments:
|
| chargebee_documentation_searchA | Only use this tool for general product documentation queries, NOT for implementation questions. Do not use this tool for code generation or implementation questions. For any developer questions about implementing Chargebee functionality (like "how to update billing address", "how to create subscription", etc.), use "chargebee_code_planner" tool instead. This tool should only be used for:
It takes the following arguments:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| chargebee-tool-selection | Guidelines for choosing the right Chargebee tool based on query type |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have explicitly distinct purposes: one for implementation guidance and code generation, the other for general documentation queries. Descriptions clearly separate their use cases, eliminating ambiguity.
Both tools follow a consistent 'chargebee_<descriptive_noun>' pattern, making it easy to infer their roles. The naming is uniform and predictable.
With only two tools, the server is very focused, but that matches its specific purpose of handling integration assistance and documentation search. While minimal, the count is reasonable for the intended scope.
The tool set covers both implementation needs (code planner) and conceptual understanding (documentation search), leaving no obvious gaps for its stated goal of answering Chargebee integration questions.