ProAbono MCP Installation
OfficialRelated Servers
Alternatives to ProAbono MCP Installation
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables coding assistants to install and configure ProAbono in a website by providing access to ProAbono documentation, the live API, and the user's own account configuration to generate integration code, inspect account data, and create test data.16MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to operate the Ribbo recurring billing API, allowing them to manage subscriptions, check entitlements, refund payments, charge immediately, and generate payment or renewal links.24MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to search API documentation, retrieve endpoint details, get SDK snippets, and check changelogs from an OpenAPI spec.264 npmMIT
- AlicenseBqualityCmaintenanceEnables AI assistants like Claude Code or Cursor to interact with a PNLCS billing panel, querying and managing clients, invoices, orders, tickets, and transactions via natural language.1524 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with the Onboarded platform through automatic API discovery and execution, with entity memory persistence and optional source code access from local repositories.-
- AlicenseNot gradedqualityAmaintenanceEnables integration with Abacate Pay API for managing payments, customers, and billing through AI assistants. Supports multi-tenancy, PIX QR codes, discount coupons, and payment simulation with secure per-request API key authentication.4 npm5MIT
TDQS
Scored across 16 tools
Most tools map cleanly to distinct resources and actions, and descriptions explicitly separate get_usages from list_subscriptions. However, create_customer and update_customer are both upserts on the same reference, making their boundary genuinely fuzzy, and search_documentation versus get_api_reference could be confused by an agent.
All tool names follow a lowercase snake_case verb_noun pattern, which is consistent and readable. Minor deviations exist: get_usages uses get for a plural collection where list would fit the pattern, and change_subscription uses change rather than the update verb used elsewhere.
At 16 tools, the surface is slightly above the typical well-scoped range, but the extra tools are justified by the server's dual purpose of subscription lifecycle management and installation/documentation support. No tool feels purely redundant, though the count is on the heavier side.
The core lifecycle is well covered: customers can be created, read, and updated; subscriptions can be listed, created, and changed; and offers, features, and usages are readable. Minor gaps remain, such as no list_customers or direct get_subscription-by-ID, and invoice/payment data is only referenced through the portal rather than exposed as tools.