← All integrations

Labs64 NetLicensing MCP server

29 operations0 webhooks

Manage NetLicensing products, product modules, license templates, licensees and licenses, validate a licensee at run time, and read transactions.

Try Labs64 NetLicensing with your agent

Connect Labs64 NetLicensing, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Labs64 NetLicensing on my account, then run one read-only example and show me the result.

Runs once, when you ask

Labs64 NetLicensing tools and triggers

Tools are what your agent can do in Labs64 NetLicensing through Corsair's MCP server. Triggers are the Labs64 NetLicensing events a routine can start from.

Licensees

  • CreateWrite

    Create a licensee for a product.

    licensees.create

  • DeleteDestructive

    Delete a licensee; forceCascade also deletes its licenses.

    licensees.delete

  • GetRead-only

    Get one licensee by number.

    licensees.get

  • ListRead-only

    List licensees (the vendor's customers).

    licensees.list

  • TransferDestructive

    Move every license of a source licensee (marked for transfer) to this licensee; NetLicensing then removes the source licensee.

    licensees.transfer

  • UpdateWrite

    Update a licensee.

    licensees.update

  • ValidateDestructive

    Check which product modules a licensee may use; floating checkouts and pay-per-use counts change unless dryRun is true.

    licensees.validate

License Templates

  • CreateWrite

    Create a license template in a product module.

    licenseTemplates.create

  • DeleteDestructive

    Delete a license template; forceCascade also deletes its licenses.

    licenseTemplates.delete

  • GetRead-only

    Get one license template by number.

    licenseTemplates.get

  • ListRead-only

    List license templates.

    licenseTemplates.list

  • UpdateWrite

    Update a license template.

    licenseTemplates.update

Connect Labs64 NetLicensing to Claude, ChatGPT or Cursor

  1. 1

    Connect Labs64 NetLicensing in Corsair

    Add your Labs64 NetLicensing API key once in Corsair. Corsair stores the credential encrypted and makes the Labs64 NetLicensing API calls for your agent, so it never goes into a prompt or a config file. Connect Labs64 NetLicensing

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Labs64 NetLicensing. On a ChatGPT personal plan, connect Labs64 NetLicensing here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Labs64 NetLicensing's read and write operations run right away and its 7 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/labs64netlicensing, add the Labs64 NetLicensing plugin, and connect with an API key. Then call methods like corsair.labs64netlicensing.api.licensees.create() from your app. Corsair syncs data per tenant.

Yes. Labs64 NetLicensing requires an API key from your Labs64 NetLicensing account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Labs64 NetLicensing, GitHub, Notion, Stripe, and the rest. Trigger Labs64 NetLicensing from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for manage NetLicensing products, product modules, license templates, licensees and licenses, validate a licensee at run time, and read transactions. Common builds include sync jobs, admin tooling, and agents that call Labs64 NetLicensing APIs from your backend. Local DB entities let you query synced Labs64 NetLicensing records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Labs64 NetLicensing API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/labs64netlicensing in the open repo. When Labs64 NetLicensing ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Labs64 NetLicensing data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Labs64 NetLicensing data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Labs64 NetLicensing on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 7 destructive Labs64 NetLicensing operations. You can change a link's mode at hub.corsair.dev/me.