mcp-server-creem
Related Servers
Alternatives to mcp-server-creem
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceUniversal billing gateway for MCP servers. Add Stripe subscription billing to any MCP server with one line of code. Supports tiered plans, usage tracking, and automatic access control.12MIT
- AlicenseBqualityCmaintenanceAn MCP server implementation that integrates with LicenseSpring APIs, providing comprehensive license management and customer operations capabilities.182 npm3MIT
- AlicenseNot gradedqualityAmaintenanceUnofficial MCP server for the Apps API that enables managing customers, payments, plans, coupons, and Discord integration through natural language.172 npm2MIT
- AlicenseDqualityDmaintenanceMCP server for managing Pterodactyl game panel resources (users, servers, nodes, locations, etc.) via the Application API.503MIT
- AlicenseBqualityBmaintenanceMCP server to help manage a WHMCS installation.6226 npm20MIT
- FlicenseBqualityCmaintenanceMCP server for the Kraviona platform API, providing tools for posts, categories, services, client enquiries, website settings, crawler files, AI drafts, and the keyword queue.21-
TDQS
Scored across 19 tools
Each tool targets a distinct action (activate, deactivate, validate, cancel, update, upgrade, create, get, list, search) on a specific resource (license, subscription, checkout, discount, product, customer, transaction). There is no overlap in functionality, and descriptions clearly differentiate them.
All tool names follow a consistent verb_object pattern with underscores (e.g., activate_license, create_checkout, list_customers). The verbs are varied but always come first, and the naming is predictable across the entire set.
19 tools cover the essential operations for a payment, subscription, and licensing platform without being excessive. Each tool serves a clear purpose, and the count is well-scoped for the domain.
The tool surface covers core CRUD and lifecycle operations for products, subscriptions, licenses, discounts, and customers. Minor gaps exist (e.g., no product update/delete, no direct subscription creation via tool), but these are acceptable given the checkout-based flow.