How to integrate NetLicensing MCP with Claude Code

Manage your NetLicensing directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: Via Composio Connect - Direct and easiest approach Via Composio SDK - Programmatic approach with more control

NetLicensing logoNetLicensing
Api Key

NetLicensing is a software license management platform for products, license models, licensees, licenses, and commerce workflows. It helps teams control entitlements, automate licensing operations, and manage software monetization in one place.

21 Tools

Introduction

Manage your NetLicensing directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate NetLicensing with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting NetLicensing to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

What is the NetLicensing MCP server, and what's possible with it?

The NetLicensing MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your NetLicensing account. It provides structured and secure access to your products, licensing models, license templates, licensees, licenses, bundles, and transactions, so your agent can configure licensing structures, assign licenses, validate licensees, manage floating sessions, and maintain licensing records on your behalf.

  • Product and licensing setup: Have your agent create and update products, configure product modules, review supported licensing options, and define license templates.
  • Licensee and license provisioning: Let the agent create licensees, assign licenses from templates or bundles, update license details, and transfer eligible licenses between licensees.
  • License validation and floating sessions: Direct your agent to validate active licenses and check floating license sessions in or out for a licensee.
  • Bundle and commerce management: Instruct your agent to create or update purchasable bundles and issue their associated licenses to licensees.
  • Licensing record administration: Have your agent list or retrieve products, modules, templates, licensees, licenses, transactions, and bundles, or delete resources you no longer need.

Connecting NetLicensing via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here NetLicensing) for even more tool search precision. It's secure and reliable.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A NetLicensing account
  • Basic knowledge of Python or TypeScript
2

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

3

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)
5

Install Composio library

npm install @composio/core dotenv

Install the Composio TypeScript library to create MCP sessions.

  • @composio/core provides the core Composio functionality
  • dotenv loads environment variables from your .env file
6

Generate Composio MCP URL

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['netlicensing'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http netlicensing-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Create a script to generate a Composio MCP URL for NetLicensing. This URL will be used to connect Claude Code to NetLicensing.

What's happening

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for NetLicensing
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it
7

Run the script and copy the MCP URL

node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts

Run your TypeScript script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output
8

Add NetLicensing MCP to Claude Code

bash
claude mcp add --transport http netlicensing-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (netlicensing-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

9

Verify the installation

bash
claude mcp list

Check that your NetLicensing MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your netlicensing-composio entry in the list
  • This confirms that Claude Code can now access NetLicensing tools

If everything is wired up, you should see your netlicensing-composio entry listed:

Claude Code MCP list showing the toolkit MCP server
10

Authenticate NetLicensing

The first time you try to use NetLicensing tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with NetLicensing
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the NetLicensing authorization flow
  • Return to the terminal and start using NetLicensing through Claude Code

Once authenticated, you can ask Claude Code to perform NetLicensing operations in natural language. For example:

  • "List active licenses expiring this month"
  • "Create licensee for new customer"
  • "Update product license model pricing"

Complete Code

Here's the complete code to get you started with NetLicensing and Claude Code:

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['netlicensing'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http netlicensing-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Conclusion

You've successfully integrated NetLicensing with Claude Code using Composio's MCP server. Now you can interact with NetLicensing directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for NetLicensing operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various NetLicensing operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

TOOLS

Supported Tools

Every NetLicensing action and event your agent gets out of the box.

Check In Licensee Session

Return and release a NetLicensing floating-license session for a licensee and return the validation results and provider cache TTL when supplied.

Check Out Licensee Session

Allocate a NetLicensing floating-license session for a licensee and return the validation results with their cache TTL.

Create Bundle

Create a purchasable NetLicensing bundle from existing license templates.

Create License

Assign a license from a license template to a licensee.

Create Licensee

Create a licensee under a product so licenses can be assigned and validated.

Create Licenses From Bundle

Create one or more licenses for a licensee from the license templates associated with a bundle.

Create License Template

Create a license template under a product module using a supported license type.

Create Product

Create a NetLicensing product that can contain product modules and licensees.

Create Product Module

Create a licensing-model-specific module under a NetLicensing product.

Delete Resource

Permanently delete a product, product module, license template, licensee, license, or bundle by number.

Get Resource

Get one product, product module, license template, licensee, license, transaction, or bundle by its NetLicensing number.

List Licensing Options

Return the supported licensing models and license types used when configuring product modules and license templates.

List Resources

List one page of products, product modules, license templates, licensees, licenses, transactions, or bundles for the connected vendor.

Transfer Licenses

Irreversibly transfer all eligible licenses from a source licensee marked for transfer to a target licensee in the same product.

Update Bundle

Update selected bundle details or replace its complete set of license templates.

Update License

Update a license's identity/number, name, parent-feature relationship, status, timing, pricing, visibility, or quantity.

Update Licensee

Update selected status, identity, transfer, or non-secret custom properties of a licensee.

Update License Template

Update selected pricing, visibility, limits, or license behavior on a license template.

Update Product

Update selected properties of an existing product; supplying discounts replaces the complete discount set, and an empty discounts list clears all discounts by sending one empty discount field.

Update Product Module

Update selected properties and model-specific settings of a product module.

Validate Licensee

Validate a NetLicensing licensee's active licenses and return the validation results with their cache TTL.

FAQ

Frequently asked questions

With a standalone NetLicensing MCP server, the agents and LLMs can only access a fixed set of NetLicensing tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from NetLicensing and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right NetLicensing tools.

Yes, absolutely. You can configure which NetLicensing scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your NetLicensing data and credentials are handled as safely as possible.

Start with NetLicensing.It takes 30 seconds.

Managed auth, hosted MCP servers, and every NetLicensing tool your agent needs.Free to start.

Start building