@chargebee/mcpofficial
A
licenseA
qualityF
maintenanceMCP Server that connects AI agents to Chargebee Platform.
2
54
16
MIT
mcp-server-vanmoof
Related Servers
Alternatives to mcp-server-vanmoof
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to interact with the commercetools Composable Commerce platform. It provides tools for managing products, categories, orders, carts, and customer data through secure read and write operations.13MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for integrating with Bika.ai platform, enabling AI assistants to perform CRUD operations on databases, manage attachments, and utilize automation and webhooks.1MIT
- AlicenseCqualityDmaintenanceMCP server for Plane integration, enabling AI agents to interact with Plane APIs and services for project management tasks.100MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for the Solid protocol enabling AI models to read, write, search, and manage resources in Solid pods.1MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that exposes Smartcar's vehicle API as tools, enabling AI agents to query vehicle telemetry and send commands using natural language.-
TDQS
B3.3/5.0
Scored across 7 tools
Disambiguation2/5
Multiple tools have overlapping purposes that could cause confusion. get_city_rides_thisweek, get_rides_summary, and get_world_rides_thisweek all return similar ride summary data with only subtle differences in scope (city vs. world vs. general). get_rides_for_week also overlaps with these but adds a date parameter, creating ambiguity about when to use which summary tool.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with 'get_' prefix and snake_case naming. The naming is perfectly predictable across all seven tools, making it easy to understand the pattern and anticipate tool names.
Tool Count4/5
Seven tools is a reasonable number for a bike sharing/ride tracking API. While the count is appropriate, the tools feel slightly redundant rather than each earning its distinct place due to the overlapping summary tools.
Completeness3/5
The server provides good read operations for customer data, preferences, cities, and rides, but lacks any write/update capabilities. For a rider data API, there are notable gaps - no tools to update preferences, log new rides, or modify customer information, which limits agent workflows to read-only operations.
Maintenance
ActivityInactive
ResponsivenessNo issues