F
licenseNot graded
qualityD
maintenanceA server that integrates with Cursor IDE to provide code review functionality for Azure repositories, enabling AI-powered pull request analysis and feedback.
2
-
Chargebee MCP Server
by ampcome-mcps
Related Servers
Alternatives to Chargebee MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA sophisticated server that enables AI assistants to automatically analyze codebases and generate comprehensive, professional documentation.2MIT
- FlicenseNot gradedqualityDmaintenanceA local server that provides powerful code analysis and search capabilities for software projects, helping AI assistants and development tools understand codebases for tasks like code generation and refactoring.4-
- FlicenseNot gradedqualityDmaintenanceThis MCP server provides AI coding assistants with curated Adobe developer knowledge on demand, enabling automatic retrieval of guidance and patterns for building App Builder actions and Workfront extensions.1-
- FlicenseNot gradedqualityDmaintenanceAn all-in-one Model Context Protocol (MCP) server that connects your coding AI to numerous databases, data warehouses, data pipelines, and cloud services, streamlining development workflow through seamless integrations.4-
- AlicenseAqualityCmaintenanceAn MCP server for KG Financial's payment services integration, enabling AI coding tools to generate accurate code by automatically searching payment integration documentation through natural language queries.66 npmMIT
TDQS
A3.6/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct purposes: chargebee_code_planner is for implementation/code generation questions, while chargebee_documentation_search is for general documentation queries. The descriptions explicitly differentiate them with clear boundaries and usage instructions, leaving no room for confusion.
Naming Consistency5/5
Both tools follow a consistent naming pattern: 'chargebee_' prefix followed by a descriptive compound noun (code_planner, documentation_search). The naming is uniform, predictable, and clearly indicates the tool's function without mixing conventions.
Tool Count2/5
With only 2 tools, the server feels severely under-scoped for a comprehensive Chargebee integration domain. While the tools cover documentation and code planning, there are no direct operational tools for CRUD actions on subscriptions, customers, or invoices, which are core to billing systems.
Completeness2/5
The toolset is incomplete for a Chargebee integration server. It lacks essential CRUD operations (e.g., create_subscription, update_customer, list_invoices) and lifecycle management tools, forcing agents to rely solely on generated code rather than direct API interactions. This creates significant gaps for automated workflows.