LicenseSpring MCP Server
This server exposes LicenseSpring License API tools for license lifecycle, consumption, trials, device variables, floating/offline use, SSO, and distribution.
Activate, check, and deactivate online licenses using license key, hardware ID, and product.
Activate and deactivate offline licenses for air-gapped use.
Add consumption units to a license or a specific feature, including optional overages.
Generate trial license keys and retrieve product details.
Track and retrieve custom device variables.
Borrow and release floating licenses, including offline borrowing.
Change passwords for user-based licenses.
Get available software versions and installation file download info.
Get an SSO URL for customer portal access.
Retrieve customer license users for a specific license.
Note: the schema covers the License API only; no Management API tools are present.
Provides Docker images for both License API and Management API servers, enabling containerized deployment of the LicenseSpring MCP functionality.
Supports configuration through .env files for setting up API credentials and environment variables needed for LicenseSpring integration.
Supports automated release workflows and versioning through GitHub integration, with features for creating GitHub releases based on commit triggers or manual dispatch.
Enables automated releases and distribution through GitHub Actions workflows, supporting semantic release based on conventional commit messages.
Runs on Node.js runtime, with specific version requirements (20.x or higher) for optimal compatibility with the LicenseSpring MCP server.
Supports distribution and installation via npm packages, with automated release versioning and NPM distribution capabilities.
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., "@LicenseSpring MCP Server activate license ABC123 for hardware ID XYZ789"
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.
LicenseSpring® MCP Server
Model Context Protocol servers for the LicenseSpring License API and Management API. They let Claude and other MCP clients activate and check licenses, track consumption, manage floating and offline licenses, and administer orders, customers, users and devices.
Two servers ship in one package so you can grant only the access you need:
Server | Binary | API | Tools |
License API |
|
| 27 |
Management API |
|
| 41 |
Synced against the LicenseSpring documentation as of October 2026. See docs/API_COVERAGE.md for the full tool → endpoint map.
Requirements
Node.js 22.14+ (or Docker)
LicenseSpring credentials from the portal under Settings → Keys
Related MCP server: Civo MCP Server
Configuration
License API — choose one authentication method
Method | Variables | Notes |
API key + shared key |
| Every request is HMAC-signed. Both are required — LicenseSpring rejects unsigned requests ( |
OAuth client credentials |
| Tokens are fetched from LicenseSpring's Keycloak and refreshed automatically. Takes precedence when set. Override the token endpoint with |
Optional: LICENSE_API_URL (default https://api.licensespring.com).
The License API rejects requests whose Date header is more than 15 minutes off, so keep the host clock in sync.
Management API
Variable | Notes |
| The Management API key — the License API key/shared key do not work here. |
| Optional, default |
Logging
Logs are JSON lines on stderr (stdout carries the MCP protocol). Set LOG_LEVEL to error, warn (default), info or debug.
Usage with Claude Desktop
{
"mcpServers": {
"licensespring-license": {
"command": "npx",
"args": ["-y", "-p", "@tfedorko/licensespring-mcp-server", "licensespring-mcp-license"],
"env": {
"LICENSE_API_KEY": "your_api_key",
"LICENSE_SHARED_KEY": "your_shared_key"
}
},
"licensespring-management": {
"command": "npx",
"args": ["-y", "-p", "@tfedorko/licensespring-mcp-server", "licensespring-mcp-management"],
"env": {
"MANAGEMENT_API_KEY": "your_management_api_key"
}
}
}
}Using Claude Code:
claude mcp add licensespring-license \
-e LICENSE_API_KEY=... -e LICENSE_SHARED_KEY=... \
-- npx -y -p @tfedorko/licensespring-mcp-server licensespring-mcp-licenseDocker
docker build -t licensespring-mcp . # License API
docker build -f Dockerfile.management -t licensespring-mcp-management .
docker run -i --rm --env-file .env licensespring-mcpTools
Tools carry MCP annotations (readOnlyHint, destructiveHint, idempotentHint) so clients can ask for confirmation before destructive calls. API failures come back as tool results with isError: true and LicenseSpring's error code, e.g. HTTP 400 (license_not_found): License not found.
License API
Key-based licenses are identified by license_key; user-based licenses by username (plus password where the API requires it). Activation also supports SSO (id_token or code + customer_account_code).
Area | Tools |
Activation |
|
Offline (air-gapped) |
|
Bundles |
|
Features & consumption |
|
Floating |
|
Trials & products |
|
License lookup |
|
Device variables |
|
Distribution |
|
Users & SSO |
|
Resources: licensespring://health, licensespring://product/{product}/details. Prompts: license-troubleshooting, trial-onboarding.
Management API
List tools accept limit (≤1000), offset, order_by (prefix - for descending), documented filters, and extra_filters for anything else (e.g. {"metadata__plan": "pro"}). Responses are {count, next, previous, results}.
Area | Tools |
Licenses |
|
Bulk |
|
License config |
|
License users on a license |
|
Orders |
|
Customers |
|
License users |
|
Devices |
|
Products |
|
Resources: licensespring://health, licensespring://management/{licenses,customers,products}. Prompts: license-management-workflow, customer-analysis.
Documented API rules are enforced before any request is sent — for example update_license requires is_trial whenever validity changes, enable_maintenance_period with maintenance_duration, and rejects validity_period together with valid_duration.
Development
npm install
npm run build
npm run lint
npm test # unit tests (Jest, mocked HTTP + in-memory MCP client)
npm run test:coverage # same, with a 100% statement/branch/function/line threshold
npm run test:smoke # spawns the built binaries over stdio against a local mock HTTP server
npm run test:integration # live API tests; skipped unless credentials are set (see tests/README.md)
npm run test:all # lint + coverage + build + smokeProject layout:
src/
config.ts env → typed config (HMAC or OAuth)
license-api/server.ts License API tools, resources, prompts
management-api/server.ts Management API tools, resources, prompts
utils/http.ts API clients (signing, OAuth tokens, GET retries, errors)
utils/auth.ts HMAC request + offline payload signatures
runtime.ts / main.ts stdio transport, graceful shutdown, startup
cli.ts / index.ts CLI entry pointTroubleshooting
Symptom | Fix |
| Add the shared key from Settings → Keys, or switch to OAuth. |
| Wrong shared key, or the key pair belongs to a different company. |
| Host clock is more than 15 minutes off; sync NTP. |
| Your company enforces OAuth; set |
| LicenseSpring rate limit. Read-only GETs are retried with backoff; writes (and |
Management API | Use the Management API key, not the License API key. |
Upgrading from 2.x
3.0 is a breaking release; see CHANGELOG.md once published and docs/API_COVERAGE.md. Highlights:
LICENSE_SHARED_KEYis now required withLICENSE_API_KEY(API-key-only requests never worked against the real API). OAuth is supported as an alternative.create_licenseis replaced bycreate_order; licenses are created through orders.Fixed request formats for
bulk_update_licenses(PATCH, list body),bulk_disable_licenses,set_user_activations,import_licenses_from_csv(multipartcsv_content),activate_offline/deactivate_offline(signed base64 payload).update_licenseno longer acceptsenabled; useenable_license/disable_license.validity_periodis aYYYY-MM-DDdate.Filters renamed to the documented names (
company_name__icontains,true_email__icontains, …).activate_license/activate_offlineno longer send the undocumentedquantityparameter.
License
MIT — see LICENSE. LicenseSpring® is a trademark of its respective owner; see TRADEMARK. This project is not affiliated with LicenseSpring.
Available Tools
18 toolsactivate_licenseActivate LicenseC
Activate a license with hardware ID and product code
Inputs: hardware_id (required), license_key (required), product (required), quantity.
activate_offlineActivate License OfflineC
Activate a license for offline use with hardware ID and product code
Inputs: hardware_id (required), license_key (required), product (required), quantity.
add_consumptionAdd ConsumptionC
Add consumption units to a license
Inputs: consumptions (required), hardware_id (required), license_key (required), product (required), +2 more.
add_feature_consumptionAdd Feature ConsumptionC
Add consumption units to a specific feature
Inputs: consumptions (required), feature (required), hardware_id (required), license_key (required), +1 more.
change_passwordChange PasswordC
Change password for a user-based license
Inputs: new_password (required), password (required), username (required).
check_licenseCheck LicenseC
Check license status and validity
Inputs: hardware_id (required), license_key (required), product (required).
deactivate_licenseDeactivate LicenseC
Deactivate a license for a specific hardware ID
Inputs: hardware_id (required), license_key (required), product (required).
deactivate_offlineDeactivate License OfflineC
Deactivate a license for offline use with hardware ID and product code
Inputs: hardware_id (required), license_key (required), product (required).
floating_borrowBorrow Floating LicenseC
Borrow a floating license for offline use
Inputs: borrowed_until (required), hardware_id (required), license_key (required), product (required).
floating_releaseRelease Floating LicenseD
Release a floating license
Inputs: hardware_id (required), license_key (required), product (required).
get_customer_license_usersGet Customer License UsersC
Get customer license users for a specific license
Inputs: customer (required), product (required).
get_device_variablesGet Device VariablesC
Get tracked variables for a device
Inputs: hardware_id (required), license_key (required), product (required).
get_installation_fileGet Installation FileC
Get installation file download information
Inputs: hardware_id (required), license_key (required), product (required).
get_product_detailsGet Product DetailsC
Get detailed information about a product
Inputs: product (required).
get_sso_urlGet SSO URLC
Get Single Sign-On URL for customer portal access
Inputs: customer_account_code (required), product (required), response_type.
get_trial_keyGet Trial KeyC
Generate a trial license key for a product
Inputs: hardware_id (required), product (required).
get_versionsGet Software VersionsC
Get available software versions for a product
Inputs: hardware_id (required), license_key (required), product (required).
track_device_variablesTrack Device VariablesC
Track custom variables for a device
Inputs: hardware_id (required), license_key (required), product (required), variables (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 18 tools
Most tools have distinct purposes targeting specific license management operations, but there is some potential confusion between activate_license/activate_offline and deactivate_license/deactivate_offline pairs where the offline variants might not be immediately distinguishable from the regular ones without careful reading of descriptions. The consumption tools (add_consumption vs add_feature_consumption) also have some overlap but are reasonably differentiated.
All 18 tools follow a consistent verb_noun naming pattern with snake_case throughout. The naming convention is highly predictable with clear action-object relationships (e.g., activate_license, check_license, get_product_details, track_device_variables). No mixing of naming styles or inconsistent verb usage is present.
With 18 tools, this is slightly on the higher side but reasonable for a comprehensive license management system covering activation, deactivation, consumption tracking, floating licenses, customer management, and device variables. The count feels appropriate for the domain scope, though it might be borderline heavy for some agent workflows.
The tool set provides excellent coverage of license management workflows including core operations (activate, check, deactivate), consumption management, floating license handling, customer/user management, product information access, trial key generation, and device variable tracking. There are no obvious gaps for the stated domain, with tools supporting both online and offline scenarios.
Maintenance
Related MCP Connectors
MCP server for Lemon Squeezy — stores, products, orders, subscriptions, license keys.
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
Host any HTTP API as a standard MCP server; auto-distribute to 12+ mainstream agent platforms.
MCP Server for agents to onboard, pay, and provision services autonomously with InFlow
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA server implementation of the Model Context Protocol (MCP) that provides REST API endpoints for managing and interacting with MCP resources.-
- AlicenseAqualityDmaintenanceAn MCP server implementation that integrates with the Civo cloud platform API, providing capabilities to manage cloud instances, networks, and Kubernetes clusters.1933 npm3MIT
- AlicenseBqualityDmaintenanceThis MCP server provides comprehensive access to the Mews hospitality platform API, covering customer and company management, reservation operations, financial transactions, account management, configuration settings, and services inventory. It implements the core functionality needed for hospitalit5325 npm1MIT
- AlicenseNot gradedqualityDmaintenanceA full-featured MCP server providing seamless access to CustomGPT.ai APIs, enabling agent and conversation management through MCP-compatible clients.5MIT