Can Lyro issue, renew, or revoke a NetLicensing license?

No. This toolkit is read-only: it exposes List Licenses and List Products and nothing that writes. Lyro can tell a customer what their license record says and hand the conversation to an agent, but the license itself is still created or changed inside NetLicensing.

How does Lyro handle an account with thousands of license records?

List Licenses supports optional filtering and pagination, so Lyro narrows the request to the records that match the customer in front of it rather than pulling the whole set into a conversation.

Which NetLicensing account does Lyro read from?

The one whose credentials you connect. Both actions authenticate against that account first, so Lyro sees exactly the licenses and products those credentials are scoped to and nothing outside them.

Can Lyro check a specific license key a customer pastes into the chat?

It can look for it. There is no dedicated key-validation action here, so Lyro retrieves license records with a filter applied and reports whether one matches and what state it is in. The check is a lookup against the license list rather than a validation call.

Labs64 netlicensing MCP integration

Reads live license records and the product catalogue so entitlement questions get answered from the licensing system, not from memory.

Connect Labs64 netlicensing See all integrations

2actions available

What your agent can do with Labs64 netlicensing

Every action runs live through MCP. Nothing to build, nothing to maintain.

List products
Lyro retrieves all products in your licensing system. Your team knows what's available to assign to customers.
List licenses
Lyro retrieves all licenses across your system. Your team tracks which customers have active access.

See all 2 actions

How businesses use Labs64 netlicensing + Lyro

Each card is one request a support team gets, and the Labs64 netlicensing actions Lyro runs to close it.

Answer a license status question on the spot
Lyro pulls the customer's license record from NetLicensing and reports its current state, so a question about whether a key is still valid is answered from the licensing system rather than escalated.
List LicensesList Products
Confirm what a product edition includes
Lyro retrieves the product catalogue and matches the customer's license to the product it belongs to, so an entitlement question gets a specific answer instead of a link to the pricing page.
List ProductsList Licenses
Give an agent the license context before handoff
When a licensing problem needs a human, Lyro attaches the matching license and product records to the conversation so the agent opens it already knowing what the customer is entitled to.
List LicensesList Products

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Labs64 netlicensing actions it has and picks the ones a request needs.

01
Connect Labs64 netlicensing
Authorize the Labs64 netlicensing account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Labs64 netlicensing actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Labs64 netlicensing · Lyro

Everything else about Labs64 netlicensing

Setup, permissions, and the limits of what Lyro can do inside Labs64 netlicensing.

No. This toolkit is read-only: it exposes List Licenses and List Products and nothing that writes. Lyro can tell a customer what their license record says and hand the conversation to an agent, but the license itself is still created or changed inside NetLicensing.