proabono
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@proabono Generate the customer portal embed code for my website"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ProAbono MCP Installation — workspace
The source of the published package now lives in
SubscriptionTech/ProAbono.Mcp.Installation.
Everything @proabono/mcp-installation is built from — the server, the tests, the build scripts, the
ProAbono API contract and the documentation corpus — moved there, and is attached here as a Git
submodule of the same name.
If you arrived from the npm page of version 0.0.1, that link points here because a published npm
version's metadata is frozen. Follow the repository above; it is the same code, with its history.
Package:
@proabono/mcp-installationMCP Registry:
com.proabono/mcp-installationInstall and configure: see the README of the submodule
What this repository is
The workspace around the package: the Claude Code rules (CLAUDE.md), the project memory
(.claude/memory/), the private notes (notes/), and the submodule pointer. It ships nothing and
builds nothing.
The build, the test suite and both publications — npm and the MCP Registry — all run inside
ProAbono.Mcp.Installation/, never here.
Related MCP server: memberpass-mcp
Working on it
git clone --recurse-submodules https://github.com/SubscriptionTech/Claude.Publiable.McpInstallation.git
cd Claude.Publiable.McpInstallation/ProAbono.Mcp.Installation
npm ci && npm run typecheck && npm run build && npm testOn a clone that already exists, git submodule update --init --recursive fills the folder. The
submodule tracks main, so git submodule update --remote moves it forward; the new pointer is then
committed here like any other change.
A commit made inside the submodule belongs to the submodule's repository: push it there first, then commit the moved pointer here.
Licence
MIT. See LICENSE — the same licence the package carries.
Available Tools
16 toolschange_subscriptionChange the state of a subscription (write)A
WRITE. Moves an existing ProAbono subscription: upgrade or downgrade it to another offer, start a draft one, suspend it, or terminate it. Identify the subscription by its internal identifier, which list_subscriptions returns. Terminating is not an immediate loss of access unless immediate is set -- by default it takes effect at the end of the current term. An upgrade terminates the current subscription and creates a new one on the target offer, so the customer's rights change: re-read them afterwards with get_usages.
Inputs: action (required), subscription_id (required), bill_now, immediate, +1 more.
create_customerCreate a ProAbono customer (write)A
WRITE. Creates a ProAbono customer in the configured Segment, keyed by the reference the merchant's application uses for the logged-in user. The endpoint is an upsert on that reference: if a customer with it already exists, this updates them instead of failing. Provisioning the customer early -- at sign-up or first login -- is the recommended path, because the hosted pages and the rights read both need the customer to exist.
Inputs: customer_ref (required), name, email, language, +1 more.
create_subscriptionSubscribe a customer to an offer (write)A
WRITE. Creates a ProAbono subscription linking an existing customer to an offer. This is the API path; a customer choosing a plan themselves goes through a hosted subscription workflow instead. The subscription is created as a copy of the offer -- pass an override only where the merchant genuinely departs from their own catalogue. Set start_now to activate it immediately; a subscription left in Draft grants no rights.
Inputs: offer_ref (required), customer_ref (required), bill_now, metadata, +3 more.
generate_pricing_tableGenerate the ProAbono pricing table embedA
Generates the embed that renders the ProAbono pricing table inside a page of the merchant's site. Two flavours: anonymous for a public pricing page, or identified for a signed-in customer, who can then subscribe in place -- which needs the customer reference and the security hash. What happens when a plan is chosen is configured in the BackOffice, not in this code.
Inputs: stack (required), identified (required), target_page (required).
get_api_referenceLook up a ProAbono Live API endpoint or objectA
Returns the exact contract of a ProAbono Live API endpoint (parameters, whether each is required, request body schema, responses) or of a named object such as Customer, Subscription, Offer, Feature or Usage. Use it before calling or generating a call to the ProAbono API, so parameter names and shapes come from the contract rather than from memory.
Inputs: object, endpoint.
get_customerRetrieve one customerA
Retrieves a ProAbono customer by the reference shared with the merchant's application (ReferenceCustomer), with the Links its hosted pages are opened from. Read-only. Use it to check whether a logged-in user already exists as a ProAbono customer.
Inputs: customer_ref (required), offer_ref.
get_offerRetrieve one offerA
Retrieves a single ProAbono offer by its reference, with its Features, pricing and the Links it exposes. Read-only. Use it when the offer reference is already known.
Inputs: offer_ref (required), customer_ref.
get_server_infoProAbono server infoA
Reports the version of the ProAbono MCP Installation server and confirms that its ProAbono configuration is complete. Returns variable names only -- never a key, a secret or an account identifier. Use it to check the server is reachable and configured before running an installation.
Inputs: no named parameters.
get_usagesRead a customer's rightsA
Reads a customer's Usages: what that customer may do right now, as ProAbono sees it, one entry per Feature carried by their running subscriptions. Read-only. This is the source an application gates access on -- never the offer reference. An empty result is ambiguous: check the customer's subscriptions with list_subscriptions before concluding they have no rights.
Inputs: customer_ref (required), feature_ref.
install_customer_portalInstall the ProAbono Customer Portal in a pageA
Generates the code that embeds the ProAbono Customer Portal inside a page of the merchant's own site -- current plan, invoices, payment method, billing address, usage -- for the signed-in customer. This is step 1 of the In-Site installation. Returns the server-side security hash computation, the route that renders the page, and the snippet to place in the template. Requires an authenticated customer area: the hosted pages always render for an identified customer.
Inputs: stack (required), target_page (required), pass_language.
list_featuresList the Features defined on the businessA
Lists the ProAbono Features of the account: the definitions the business owns, each with its type (OnOff, Limitation or Consumption). Read-only. These are what an application can gate access on. A Feature is the definition; a customer's value for it is a Usage, read with get_usages. Reads every page.
Inputs: visible_only.
list_offersList the offers of the accountA
Lists the ProAbono offers the configured Segment exposes, with the Features each one carries and its pricing. Read-only. Use it to show a catalogue, to pick the offer a subscription or a pricing table targets, or to check the prerequisite that at least one offer exists and carries at least one Feature. Reads every page, not just the first.
Inputs: customer_ref, visible_only.
list_subscriptionsList subscriptionsA
Lists ProAbono subscriptions, optionally those of one customer, with their state and the Features they carry. Read-only. Use it to see what a customer is actually subscribed to, or to explain why a customer has no rights. Reads every page.
Inputs: customer_ref.
search_documentationSearch the ProAbono installation documentationA
Answers a natural-language question about integrating ProAbono from the official installation documentation: hosted pages, the security hash, subscription workflows, rights and usage, webhooks, testing and troubleshooting. Use it before writing any ProAbono integration code, and prefer it over recalling ProAbono behaviour. Returns the matching documentation sections with their source file.
Inputs: question (required), limit.
update_billing_addressUpdate a customer's billing address (write)C
WRITE. Updates the billing address of a ProAbono customer. Only the fields passed are changed. The address is what invoices are issued against, and the tax identifier is what VAT treatment is derived from, so it must be the customer's own data -- never a placeholder.
Inputs: customer_ref (required), city, phone, region, +8 more.
update_customerUpdate a ProAbono customer (write)A
WRITE. Updates a ProAbono customer identified by its shared reference. The endpoint is an upsert: if no customer carries that reference, one is created rather than an error raised. Only the fields passed are changed. Do not pass a field the merchant's application is not the authority for -- the hosted pages let the customer edit their own name and language, and this overwrites what they set.
Inputs: customer_ref (required), name, email, language, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 16 tools
Most tools target distinct resources and actions, but create_customer and update_customer are both documented as upserts, making it genuinely ambiguous which to call. get_usages and list_subscriptions are related enough to require careful description reading, though the descriptions do clarify their difference.
All tool names follow a consistent verb_noun snake_case pattern, such as list_, get_, create_, update_, change_, install_, and generate_. There are no mixed naming conventions or vague single-word tool names.
At 16 tools, the set is slightly above the typical well-scoped range, but each tool addresses a real aspect of the ProAbono domain: customers, subscriptions, offers, features, usage, documentation, and embed generation. The count feels justified rather than bloated.
The server covers the core workflows: customer provisioning, subscription creation and changes, offer/feature lookup, rights checking, documentation search, API contract retrieval, and portal/pricing embed generation. Minor gaps exist around direct invoice/payment or offer administration tools, but those may be intentionally handled outside this MCP surface.
Maintenance
Related MCP Connectors
Embed an AI chat widget on your website from your coding agent: provision, configure, get snippet.
Set up, test and publish an AI customer support Agent for your SaaS product.
Form companies, manage bank accounts, cards, invoices and more — directly from your AI coding tools.
Let your AI assistant configure and manage TalkJS chat in your app.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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.26 npm7MIT
- AlicenseNot gradedqualityBmaintenanceConnects MCP clients like Claude and Cursor to MemberPass workspace, exposing 42 tools for managing projects, plans, subscriptions, members, access codes, payments, webhooks, and analytics.1MIT
- AlicenseAqualityDmaintenanceEnables API documentation lookup and live API tools for managing Upmind platform resources like brands, products, clients, invoices, and tickets through natural language.971MIT
- 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