developer-tools

LicenseSpring

stier1ba

by stier1ba

Integrate LicenseSpring for advanced software license management, activation, validation, and trial key generation with

Integrates with LicenseSpring's license management platform to enable software license activation, validation, consumption tracking, customer management, and trial key generation through dual API architecture with HMAC-SHA256 authentication.

github stars

2

0 commentsdiscussion

Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.

HMAC-SHA256 authenticated API accessDual API architecture for comprehensive operationsHardware binding support

best for

  • / Software vendors implementing license protection
  • / Developers building license management workflows
  • / Companies managing trial and subscription software

capabilities

  • / Activate and validate software licenses
  • / Create and manage customers
  • / Track license consumption and usage
  • / Generate trial license keys
  • / Handle floating license operations
  • / Manage license deactivations and hardware binding

what it does

Connects to LicenseSpring's platform to manage software licenses, validate activations, track usage, and handle customer operations through their APIs.

about

LicenseSpring is a community-built MCP server published by stier1ba that provides AI assistants with tools and capabilities via the Model Context Protocol. Integrate LicenseSpring for advanced software license management, activation, validation, and trial key generation with It is categorized under developer tools.

how to install

You can install LicenseSpring in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.

license

MIT

LicenseSpring is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.

readme

LicenseSpring® MCP Server

An MCP server implementation that integrates with LicenseSpring APIs, providing comprehensive license management and customer operations capabilities.

Features

  • License Operations: Activate, check, deactivate licenses with hardware binding
  • Customer Management: Create, list, and manage customers
  • Usage Tracking: Monitor license consumption and feature usage
  • Trial Management: Generate and manage trial licenses
  • Floating Licenses: Handle floating license operations
  • Authentication Priority: LICENSE_API_KEY as primary method, LICENSE_SHARED_KEY optional for enhanced security
  • Comprehensive Testing: Full integration test suite with real API validation

Tools

License API Tools

  • activate_license - Activate a license with hardware ID binding
  • check_license - Check license status and validity
  • deactivate_license - Deactivate a license for specific hardware
  • add_consumption - Add consumption units to a license
  • get_trial_key - Generate trial license keys
  • get_product_details - Retrieve product information
  • floating_release - Release floating licenses
  • floating_borrow - Borrow floating licenses for offline use
  • change_password - Change user passwords for user-based licenses
  • get_versions - Get available software versions
  • get_installation_file - Get installation file information
  • get_sso_url - Generate Single Sign-On URLs

Management API Tools

  • list_licenses - List licenses with optional filtering
  • create_license - Create new licenses
  • update_license - Update existing licenses
  • get_license - Get detailed license information
  • delete_license - Delete licenses
  • list_customers - List customers with filtering options
  • create_customer - Create new customers

Configuration

Getting API Credentials

  1. License API Key: Log into your LicenseSpring dashboard → Settings → Keys (PRIMARY authentication method)
  2. Management API Key: Same location, copy your Management API Key
  3. Shared Key: Optional for organizations using shared API settings (provides enhanced security)

Testing

Run the comprehensive integration test to validate functionality:

# Build the project
npm run build

# Run integration tests against real LicenseSpring API
npm run test:integration

# Run unit tests
npm test

The integration test validates all 34 MCP tools against the real LicenseSpring API and verifies authentication priority works correctly. The implementation provides 100% feature parity with the LicenseSpring Postman collection.

🔧 CI/CD Integration: GitHub Actions workflows now support full integration testing with proper secret configuration.

Usage with Claude Desktop

Add this to your claude_desktop_config.json:

License API 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_IF_USING_SHARED_API_SETTINGS"
      }
    }
  }
}

Management API Server

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

Docker

{
  "mcpServers": {
    "licensespring": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "LICENSE_API_KEY",
        "-e",
        "LICENSE_SHARED_KEY",
        "stiertfedorko/licensespring-mcp:latest"
      ],
      "env": {
        "LICENSE_API_KEY": "YOUR_LICENSE_API_KEY",
        "LICENSE_SHARED_KEY": "YOUR_SHARED_KEY_OR_LEAVE_EMPTY"
      }
    },
    "licensespring-management": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "MANAGEMENT_API_KEY",
        "stiertfedorko/licensespring-mcp-management:latest"
      ],
      "env": {
        "MANAGEMENT_API_KEY": "YOUR_MANAGEMENT_API_KEY"
      }
    }
  }
}

Subscription Tier Support

The server automatically adapts to your LicenseSpring subscription tier:

  • Premium/Enterprise: Full functionality with HMAC authentication
  • Basic/Standard: Limited mode with helpful upgrade guidance
  • Development: Test mode for safe development

Note: LICENSE_SHARED_KEY is optional. The server will start regardless of your subscription tier and provide appropriate guidance for API limitations.

Usage with VS Code

For quick installation, use the one-click installation buttons below:

Install with NPX in VS Code

Install with NPX in VS Code Insiders

For manual installation, add the following JSON block to your User Settings (JSON) file in VS Code:

NPX

{
  "mcp": {
    "inputs": [
      {
        "type": "promptString",
        "id": "license_api_key",
        "description": "LicenseSpring License API Key",
        "password": true
      },
      {
        "type": "promptString",
        "id": "license_shared_key",
        "description": "LicenseSpring Shared Key (optional for Basic/Standard tiers)",
        "password": true
      }
    ],
    "servers": {
      "licensespring": {
        "command": "npx",
        "args": ["-y", "@tfedorko/licensespring-mcp-server", "license-api"],
        "env": {
          "LICENSE_API_KEY": "${input:license_api_key}",
          "LICENSE_SHARED_KEY": "${input:license_shared_key}"
        }
      }
    }
  }
}

Troubleshooting

Common Issues

Error: "npm error could not determine executable to run"

  • Solution: Update to version 1.0.1 or later: npx @tfedorko/licensespring-mcp-server@latest
  • Cause: Fixed in v1.0.1 - improved binary configuration and startup process

Error: "MCP error -1: Connection closed"

  • Solution: Update to version 1.0.2 or later: npx @tfedorko/licensespring-mcp-server@latest
  • Cause: Fixed in v1.0.2 - server now defaults to license-api mode for Claude Desktop compatibility

Error: "LICENSE_API_KEY is required"

  • Solution: Set your environment variables in .env file or Claude Desktop config
  • Check: Copy .env.example to .env and fill in your API credentials

Error: "Authentication failed"

  • Solution: Verify your API keys in the LicenseSpring dashboard
  • Note: LICENSE_SHARED_KEY is optional for Basic/Standard subscription tiers

Server starts but API calls fail

  • Check: Your LicenseSpring subscription tier and available API features
  • Solution: The server provides helpful guidance for subscription limitations

Getting Help

  1. Check the error messages - they provide specific guidance
  2. Verify your LicenseSpring subscription tier and API access
  3. Review the Advanced Documentation below
  4. Open an issue on GitHub with error details

Release Automation

This project includes comprehensive automated release versioning and NPM distribution:

Quick Release Commands

npm run release          # Patch release (1.0.0 -> 1.0.1)
npm run release:minor    # Minor release (1.0.0 -> 1.1.0)
npm run release:major    # Major release (1.0.0 -> 2.0.0)

Preview Changes

npm run version:dry      # Preview version bump
npm run publish:dry      # Preview NPM publish

Automated GitHub Releases

  • Commit triggers: Use [release] in commit messages
  • Manual dispatch: GitHub Actions workflow
  • Semantic release: Conventional commit messages

For complete automation documentation, see Release Automation Guide.

Advanced Documentation

For comprehensive guides and advanced configuration:

Installation

NPM Package

npm install -g @tfedorko/licensespring-mcp-server

Note: Requires Node.js 20.x or higher for optimal compatibility.

Docker Images

# License API Server
docker pull stiertfedorko/licensespring-mcp:latest

# Management API Server
docker pull stiertfedorko/licensespring-mcp-management:latest

Build

Docker build:

docker build -t licensespring-mcp:latest -f Dockerfile .
docker build -t licensespring-mcp-management:latest -f Dockerfile.management .

License

This MCP server is licensed und


FAQ

What is the LicenseSpring MCP server?
LicenseSpring is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
How do MCP servers relate to agent skills?
Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
How are reviews shown for LicenseSpring?
This profile displays 34 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.7 out of 5—verify behavior in your own environment before production use.

Use Cases

Extended AI Capabilities

Add new capabilities to Claude beyond text generation

Example

Access external data sources, execute code, interact with tools and services

Transform Claude from chatbot to action-taking agent

Context Enhancement

Provide Claude with access to relevant context and data

Example

Load project documentation, access knowledge bases, query databases

Get more accurate, context-aware responses

Workflow Automation

Automate multi-step workflows combining AI and external tools

Example

Research → Summarize → Create document → Send notification

Complete complex tasks end-to-end without manual steps

Implementation Guide

Prerequisites

  • Claude Desktop 0.7.0+ or Cursor IDE with MCP support
  • Basic understanding of MCP architecture and capabilities
  • Access credentials for integrated services (if required)
  • Willingness to experiment and iterate on configuration

Time Estimate

15-60 minutes depending on server complexity

Installation Steps

  1. 1.Install MCP server: npm install -g [package-name] or via GitHub
  2. 2.Add server configuration to ~/.claude/mcp.json
  3. 3.Provide required credentials and configuration
  4. 4.Restart Claude Desktop to load new server
  5. 5.Test basic functionality with simple prompts
  6. 6.Explore capabilities and experiment with use cases
  7. 7.Document successful patterns for reuse

Troubleshooting

  • MCP server not loading: Check config syntax, verify installation
  • Connection errors: Check network, firewall, credentials
  • Feature not working: Read server docs, check required parameters
  • Performance issues: Monitor resource usage, check for network latency
  • Conflicts with other servers: Check port assignments, namespace collisions

Best Practices

✓ Do

  • +Read server documentation thoroughly before setup
  • +Start with simple use cases to validate functionality
  • +Test in non-production environment first
  • +Monitor resource usage and performance
  • +Keep servers updated for bug fixes and new features
  • +Document configuration for team members
  • +Use environment variables for sensitive configuration

✗ Don't

  • Don't grant overly permissive access to MCP servers
  • Don't skip reading security considerations in docs
  • Don't expose sensitive data without proper controls
  • Don't run untrusted MCP servers without code review
  • Don't ignore error messages—investigate root cause

💡 Pro Tips

  • Combine multiple MCP servers for powerful workflows
  • Create custom MCP servers for your specific needs
  • Share successful configurations with team
  • Use MCP inspector for debugging
  • Join MCP community for tips and troubleshooting

Technical Details

Architecture

Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.

Protocols

  • Model Context Protocol (MCP)
  • JSON-RPC 2.0
  • stdio or HTTP transport

Compatibility

  • Claude Desktop
  • Cursor IDE
  • Custom MCP clients

When to Use This

✓ Use When

Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.

✗ Avoid When

Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.

Integration

  • Tool composition: Chain multiple MCP tools in workflows
  • Context augmentation: Provide AI with relevant external data
  • Action delegation: Let AI execute tasks on external systems
  • Bidirectional sync: Keep AI context and external systems in sync

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.

List & Promote Your MCP Server

Share your MCP server with the developer community

GET_STARTED →
MCP server reviews

Ratings

4.734 reviews
  • Dhruvi Jain· Dec 24, 2024

    According to our notes, LicenseSpring benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.

  • Neel Sethi· Dec 24, 2024

    I recommend LicenseSpring for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.

  • Mateo Bansal· Dec 16, 2024

    According to our notes, LicenseSpring benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.

  • Rahul Santra· Nov 23, 2024

    LicenseSpring is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.

  • Anika Chen· Nov 19, 2024

    We evaluated LicenseSpring against two servers with overlapping tools; this profile had the clearer scope statement.

  • Oshnikdeep· Nov 15, 2024

    We wired LicenseSpring into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.

  • Diego Verma· Nov 15, 2024

    LicenseSpring reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Anaya Sanchez· Nov 7, 2024

    We wired LicenseSpring into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.

  • Anaya Park· Oct 26, 2024

    LicenseSpring is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.

  • Pratham Ware· Oct 14, 2024

    We evaluated LicenseSpring against two servers with overlapping tools; this profile had the clearer scope statement.

showing 1-10 of 34

1 / 4