home / mcp / license mcp server

License MCP Server

MCP Server generated by mcp.ag2.ai

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "ag2-mcp-servers-enterprise-license-manager-api": {
      "command": "python",
      "args": [
        "mcp_server/main.py",
        "stdio"
      ],
      "env": {
        "CONFIG": "{\"transport\":\"stdio\"}",
        "SECURITY": "<SECURITY>",
        "CONFIG_PATH": "mcp_server/mcp_config.json"
      }
    }
  }
}

You run an MCP Server to expose a structured API surface for the Enterprise License Manager API licensing spec. The server lets you connect an MCP client to a local or remote endpoint, enabling standardized, context-aware access to licensing data and actions. This guide walks you through practical usage, installation steps, and essential configuration to get you up and running quickly.

How to use

You interact with the MCP Server by starting it in one of the supported transport modes and then pointing your MCP client to the chosen endpoint. In standard usage, you run the server locally in a stdio session or expose it via an HTTP-based transport if needed. Once running, your MCP client can perform requests defined by the server’s interface, such as querying licensing information, checking statuses, or triggering contextual actions, depending on how the API is implemented for the Enterprise License Manager.

How to install

Prerequisites Your environment must have Python 3.9 or newer, and you should have pip and uv installed.

Step 1: Prepare your environment Create a project directory and switch to it.

Step 2: Install dependencies You will install the project in editable mode with development dependencies.

# 1) Clone the repository
git clone <repository-url>
cd mcp_server

# 2) Install dependencies (editable dev install)
pip install -e ".[dev]"

# If you prefer to use uv to run in editable mode
uv pip install --editable ".[dev]"

Step 3: Run the server In this setup, you start the server in stdio mode for development or testing.

python mcp_server/main.py stdio

Step 4: Configure runtime options You can customize runtime behavior via environment variables. The following are recognized by the server: - CONFIG_PATH: Path to a JSON configuration file (for example, mcp_server/mcp_config.json). - CONFIG: A JSON string containing the configuration. - SECURITY: Environment variables that control security parameters (for example, API keys). Adapt these according to your deployment needs and ensure the server sees the appropriate values before startup.

Configuration and operation notes

The server supports multiple transport modes (stdio, sse, streamable-http). For development, using stdio is the simplest path, as shown above. You can specify configuration through a file path, a JSON string, or environment variables. When you supply a configuration file, ensure it contains the settings the MCP client will rely on for the Enterprise License Manager API.

If you are integrating into a larger deployment, you may choose to run the server behind a process manager or in a container. Ensure the environment variables for security and configuration are correctly propagated to the process.

Available tools

ruff

Linting and formatting tool used to ensure code quality and style consistency.

mypy

Static type checker to verify type hints across the codebase.

pytest

Testing framework used to run unit and integration tests.

static-analysis

Run static analysis including bandit and semgrep to identify security and quality issues.

pre-commit

Pre-commit hooks that run automatically before commits to enforce standards.

hatch

Build and publish workflow for the project.