@chargebee/mcpofficial
A
licenseA
qualityF
maintenanceMCP Server that connects AI agents to Chargebee Platform.
2
32 npm
16
MIT
Codinfy MCP
by bakalagoin
Related Servers
Alternatives to Codinfy MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server that gives AI agents Lightning payments, L402 API access, trust verification, and service discovery.117 npmMIT
- AlicenseAqualityDmaintenanceMCP server for AI agents to manage ad campaigns across Google, Meta, LinkedIn, Microsoft, Reddit, TikTok, and more2151 npm17MIT
- AlicenseBqualityDmaintenanceMCP server providing AI agents access to 38 pay-per-call APIs (LLM, image, code, audio, crypto, web, IPFS) via HTTP 402 micropayments in USDC/USDm.2233 npm1MIT
- AlicenseNot gradedqualityCmaintenanceA unified MCP server providing AI agents with 40+ developer APIs including geolocation, crypto prices, DNS lookup, and web scraping. Enables natural language access to various tools through a single gateway.1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for AgentPay — the payment gateway for autonomous AI agents. Fund a wallet once, give your agent the key, and it discovers, provisions, and pays for tool APIs on its own. One key, every tool.112 npm1MIT
TDQS
A3.5/5.0
Scored across 17 tools
Disambiguation5/5
All 17 tools have clearly distinct purposes. Each targets a specific resource and action (e.g., license validation vs. status check, brand assets vs. settings). There is no overlap that would confuse an agent.
Naming Consistency5/5
All tools use a consistent verb_noun snake_case pattern (e.g., create_checkout, get_product, list_ad_units). Even OAuth tools follow this implicitly. No mixing of conventions.
Tool Count4/5
17 tools cover multiple subdomains (licensing, payments, ads, branding, marketplace, auth, analytics). While slightly above the typical 15-tool threshold, each tool serves a distinct need and the count is justified for the platform's breadth.
Completeness4/5
The tool surface covers key read operations and essential writes (checkout creation, event tracking) across all subdomains. Minor gaps exist (e.g., no product creation or license revocation), but for a client-facing API these are acceptable and do not hinder common workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues