MCP Installation

ProAbono MCP Installation

A local MCP server that installs ProAbono into your site, from your IDE.

It gives your coding assistant the ProAbono documentation, the API Live contract and *your own* ProAbono configuration, so it can run the In-Site installation with you end to end, generate integration code already filled in with your real business identifier, Segment, offers and Features, read your account back to verify the result, and answer API questions from the real contract instead of guessing.

It runs locally, over stdio, against whatever account your credentials open. It has no environment concept of its own: your credentials are the only boundary.

Install

Claude Code

claude mcp add --transport stdio proabono --scope user -- npx -y @proabono/mcp-installation

VS Code

In .vscode/mcp.json:

{

"servers": { "proabono": { "type": "stdio", "command": "npx", "args": ["-y", "@proabono/mcp-installation"] } } }

Cursor

In .cursor/mcp.json (or ~/.cursor/mcp.json for every project):

{

"mcpServers": { "proabono": { "command": "npx", "args": ["-y", "@proabono/mcp-installation"] } } }

Requires Node.js 20 or later.

Configuration

The server reads seven environment variables and nothing else. It refuses to start if any is missing, naming the ones it needs.

All seven are in your ProAbono BackOffice, on one page: *Integration → MCP*. PROABONO_API_BASE must begin with https://, and PROABONO_BUSINESS_ID must be digits only.

Put them in the `env` block of your MCP client entry, in a file git ignores. That keeps each set of seven attached to one project and one ProAbono account — which is what you need once you have two sets, since sandbox and production are two accounts with different endpoints, identifiers and keys. Declare one entry per account, for example proabono-sandbox and proabono-production, each with its own env.

• .vscode/mcp.json and .cursor/mcp.json sit inside your repository: add them to .gitignore before pasting a value into them. Cursor also reads ~/.cursor/mcp.json, outside every repository.
• Claude Code: --scope user keeps the entry outside the repository. A project .mcp.json is normally committed, so write ${PROABONO_API_KEY} and the other six there instead of the values — Claude Code expands them from your environment.
• VS Code can also prompt for a value through the inputs section of mcp.json, which keeps it out of the file.
• Avoid shell exports: they hold one set per shell and per machine, and hand your production keys to every project you open.
• The server does not read a .env file. It reads its process environment only.

No value you supply is ever logged, returned by a tool, put in an error message, or inlined into generated code. Generated code references the variable names.

First prompt

With the server added and the seven variables set, open your project and paste this into your assistant:

Help me install ProAbono in this project.

1. Call get_server_info to confirm the server is reachable, and tell me which version you are talking to.
2. Call installation_status to see whether an installation was already started here.
3. Run install_insite: tell me which stack you detected and why, check the prerequisites with me, then take me through the three In-Site steps and the notification endpoint in order, placing the generated code where my signed-in user is known.
4. List what I still have to do by hand in the ProAbono BackOffice.
5. When the code is in place, run verify_insite_installation and walk me through the go-live checklist.

Answer every question about the ProAbono API from search_documentation and get_api_reference, never from memory.

When it works, step 1 answers with the server version and a configuration whose status is complete, listing the seven variable names — never a value. If the ProAbono tools are not there at all, the server refused to start: a variable is missing, and the error naming it is in your MCP client's log. get_server_info never reports an incomplete configuration, because the server does not start on one.

The generators return code and edit none of your files; your assistant places it. The one file the server writes is .proabono/installation.json, the installation state: it carries no credential, is meant to be committed so a later session resumes where this one stopped, and is not written when a tool is called with record_state: false.

Point your keys at a Sandbox account to run this. verify_insite_installation makes sure the customer it verifies against exists — it creates one under an mcp-verify- reference when you name none — and the tools that usually come next — create_update_customer, create_subscription, the Usage writes, bill_customer — create real data in whatever account your credentials open.

Example prompts

Once the installation is under way, these are the questions a developer asks next. Your assistant picks the tools; the second column is the ones it usually reaches for.

What it covers today

The version you installed is in CHANGELOG.md, and get_server_info reports it:

• The three In-Site steps, end to end: the Customer Portal embed with its security hash, the Subscription Workflow round trip, and the Usage synchronization with its cache, its gate and its resynchronization.
• The notification endpoint, with signature verification, deduplication and the BackOffice procedure that activates it.
• Verification: steps 2 and 3 exercised against your account, the go-live rules checked against your own files, and the twelve-item checklist.
• Catalogue and account introspection: offers, Features, customers, subscriptions, Usages, invoices.
• Writes across the lifecycle: customers and their settings, billing addresses, subscriptions and each of their four transitions, Usage writes for all three Feature types, balance lines and billing.
• Documentation and API reference: natural-language search over the ProAbono corpus and the API Live contract.

Not in it, and planned: advanced In-Site options — CSS customization of the hosted pages, and further specific workflows.

Widget and plug-in installations (WordPress and similar) are out of scope by design: this server installs ProAbono In-Site, by code, whatever your stack would lend itself to.

Offers, Features, webhooks, pricing pages and the workflow redirect URL are configured in your ProAbono BackOffice, and the API cannot create them: the server reads them, names what is missing, and gives you the BackOffice path.

Tools

*Writes* marks a tool that changes data in the account your credentials open. It runs as soon as your assistant calls it, with no confirmation step: your credentials are the only boundary.

Documentation

Installation

Code generation

Catalogue

Customers

| anonymize_customer | Irreversible. The GDPR erasure path: it erases the person