proabono
# ProAbono MCP Installation — workspace
**The source of the published package now lives in
[SubscriptionTech/ProAbono.Mcp.Installation](https://github.com/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-installation`](https://www.npmjs.com/package/@proabono/mcp-installation)
- **MCP Registry**: `com.proabono/mcp-installation`
- **Install and configure**: see the
[README of the submodule](https://github.com/SubscriptionTech/ProAbono.Mcp.Installation#readme)
## 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.
## Working on it
```bash
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 test
```
On 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](LICENSE) — the same licence the package carries.
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.