Summary

Two servers, because reading a licence and administering one need different keys.

The split is a security boundary, not packaging convenience: a client wired to the License API can activate and check, and cannot create or delete anything. Add the management server only where that authority belongs. Note that what actually works depends on your LicenseSpring tier — the server starts either way and reports the limitation rather than hiding it.

What it is

A LicenseSpring integration that ships as two separate server entry points. The License API side handles what an installed product does — activation against a hardware id, status checks, consumption, floating licences. The Management API side is the back office: listing, creating and updating licences and customers.

What you get

Licences activated and deactivated against a hardware id, and checked for status and validity — `activate_license`, `check_license`, `deactivate_license`
Consumption units added, and trial keys generated — `add_consumption`, `get_trial_key`
Floating licences released, and borrowed for offline use — `floating_release`, `floating_borrow`
Product, version and installer information, plus SSO URL generation and password change for user-based licences — `get_product_details`, `get_versions`, `get_installation_file`, `get_sso_url`, `change_password`
Management-side licence lifecycle: list with filters, create, read, update, delete — `list_licenses`, `create_license`, `get_license`, `update_license`, `delete_license`
Customers listed with filters and created — `list_customers`, `create_customer`

Requirements

A LicenseSpring account. `LICENSE_API_KEY` is the primary credential for the licence server, taken from the dashboard under Settings → Keys; `LICENSE_SHARED_KEY` is optional and only for organisations on shared API settings. The management server takes `MANAGEMENT_API_KEY` instead. Node.js 20.x or higher; the two servers run from the two Docker images. The README launches them instead from `@tfedorko/licensespring-mcp-server`, taking `license-api` or `management-api` as the argument, a name npm does not have. Behaviour adapts to your subscription tier — Basic and Standard run in a limited mode rather than failing to start.