How to integrate NetLicensing MCP with Claude Agent SDK

This guide walks you through connecting NetLicensing to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working NetLicensing agent that can create products, add licensees, issue licenses, manage license sessions, and delete resources through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a NetLicensing account through Composio's NetLicensing MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for freeGet a demo
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

This guide walks you through connecting NetLicensing to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working NetLicensing agent that can create products, add licensees, issue licenses, manage license sessions, and delete resources through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a NetLicensing account through Composio's NetLicensing MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate NetLicensing with

OpenAI Agents SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for NetLicensing
  • Configure an AI agent that can use NetLicensing as a tool
  • Run a live chat session where you can ask the agent to perform NetLicensing operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

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 step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A NetLicensing account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with NetLicensing functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  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 composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for NetLicensing
  const session = await composio.create(USER_ID, {
    toolkits: ['netlicensing'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for NetLicensing
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to NetLicensing tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to NetLicensing
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

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

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  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 composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['netlicensing']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to NetLicensing tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with NetLicensing through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
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.

FRAMEWORKS

How to build NetLicensing MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use NetLicensing MCP with OpenAI Agents SDK

Claude Code logo

Claude Code

Use NetLicensing MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use NetLicensing MCP with Claude Cowork

Codex logo

Codex

Use NetLicensing MCP with Codex

OpenClaw logo

OpenClaw

Use NetLicensing MCP with OpenClaw

Hermes logo

Hermes

Use NetLicensing MCP with Hermes

CLI logo

CLI

Use NetLicensing MCP with CLI

Google ADK logo

Google ADK

Use NetLicensing MCP with Google ADK

LangChain logo

LangChain

Use NetLicensing MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use NetLicensing MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use NetLicensing MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use NetLicensing MCP with LlamaIndex

CrewAI logo

CrewAI

Use NetLicensing MCP with CrewAI

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 Agent SDK 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
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies