LicenseSpring

Provides license activation, validation, trial management, and customer operations via MCP for LicenseSpring APIs.
  • javascript

2

GitHub Stars

javascript

Language

4 months ago

First Indexed

3 weeks ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "stier1ba-licensespring-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@tfedorko/licensespring-mcp-server",
        "license-api"
      ],
      "env": {
        "LICENSE_API_KEY": "YOUR_LICENSE_API_KEY",
        "LICENSE_SHARED_KEY": "YOUR_SHARED_KEY_IF_USING_SHARED_API_SETTINGS",
        "MANAGEMENT_API_KEY": "YOUR_MANAGEMENT_API_KEY"
      }
    }
  }
}

You can manage licenses, customers, and usage through a dedicated LicenseSpring MCP Server that integrates with LicenseSpring APIs. This server provides license activation, validation, trial management, and floating licenses, all accessible via MCP clients. It is designed to help you control licensing workflows from a centralized, programmatic interface.

How to use

Use an MCP client to connect to the LicenseSpring MCP Server and perform typical license operations. You can activate licenses with hardware binding, check license validity, deactivate licenses on specific hardware, and track usage. You can also generate trial licenses, borrow floating licenses for offline use, and manage customers. Authentication is primarily via LICENSE_API_KEY, with an optional LICENSE_SHARED_KEY for enhanced security. Ensure your client config includes the appropriate keys and points to the MCP endpoints described in the configuration examples.

How to install

Prerequisites: you need Node.js 20.x or higher for optimal compatibility. You will also use npm and npx to run the MCP server components.

Install the MCP server package globally so you can run the MCP server commands from anywhere.

Run the LicenseSpring MCP Server for the License API endpoint to start handling license operations.

Run the Management API Server to manage licenses, customers, and related configuration.

Configuration and server setup

Two standard ways to run the MCP server are shown below. Use the License API server for license-related actions and the Management API server for administrative tasks. Each server expects environment variables for API keys.

{
  "mcpServers": {
    "licensespring": {
      "command": "npx",
      "args": [
        "-y",
        "@tfedorko/licensespring-mcp-server",
        "license-api"
      ],
      "env": {
        "LICENSE_API_KEY": "YOUR_LICENSE_API_KEY",
        "LICENSE_SHARED_KEY": "YOUR_SHARED_KEY_IF_USING_SHARED_API_SETTINGS"
      }
    },
    "licensespring-management": {
      "command": "npx",
      "args": [
        "-y",
        "@tfedorko/licensespring-mcp-server",
        "management-api"
      ],
      "env": {
        "MANAGEMENT_API_KEY": "YOUR_MANAGEMENT_API_KEY"
      }
    }
  }
}

Security and authentication

Your primary authentication method is the License API Key. You can add a Shared Key for enhanced security if your organization uses shared API settings. Ensure that your MCP client stores these keys securely and never exposes them in logs or public repositories.

Usage with Claude Desktop

Set up the License API Server configuration in Claude Desktop to route license API requests through the MCP server.

{
  "mcpServers": {
    "licensespring": {
      "command": "npx",
      "args": ["-y", "@tfedorko/licensespring-mcp-server", "license-api"],
      "env": {
        "LICENSE_API_KEY": "YOUR_LICENSE_API_KEY",
        "LICENSE_SHARED_KEY": "YOUR_SHARED_KEY"
      }
    }
  }
}

Troubleshooting and tips

If you encounter common issues, verify your API keys are correctly configured and that your subscription tier supports the features you are trying to use. The server will guide you with relevant messages for any API limitations based on your tier. If authentication fails, double-check the keys in your LicenseSpring dashboard and ensure they are loaded into your environment.

Available tools

activate_license

Activate a license and bind it to a hardware ID to enforce usage on a specific device.

check_license

Query a license to verify status, validity, and usage details.

deactivate_license

Deactivate a license for a given hardware ID, releasing it for other devices.

add_consumption

Add usage units to a license to reflect increased consumption.

get_trial_key

Generate trial license keys for evaluation periods.

get_product_details

Retrieve information about licensed products.

floating_release

Release floating licenses back to the pool for others to use.

floating_borrow

Borrow floating licenses for offline or delayed connectivity scenarios.

change_password

Change user passwords for user-based licenses.

get_versions

Get available software versions for deployment.

get_installation_file

Fetch installation file information for a given product.

get_sso_url

Generate Single Sign-On URLs for seamless authentication.

list_licenses

List licenses with optional filtering.

create_license

Create new licenses with given attributes.

update_license

Update existing licenses with new details.

get_license

Get detailed information about a specific license.

delete_license

Delete licenses from the system.

list_customers

List customers with filtering options.

create_customer

Create new customers in the system.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational