Integrate Monaiq
This page gives you the three ways to integrate Monaiq and tells you which one to pick.
Whichever you choose, the job is the same: your product asks Monaiq what the customer in front of it is licensed for, and behaves accordingly.
1. AI-assisted, with the Monaiq plugin
Section titled “1. AI-assisted, with the Monaiq plugin”Install the Monaiq plugin into Claude Code with two commands, sign in with a code we email you, and work in your own editor. The plugin brings tools that build your catalog for you (products, features, offerings) and tools that produce the integration itself: the base wiring, a feature check, and an embedded purchase flow if you want customers to buy from inside your product.
The guidance tools return instructions and snippets rather than editing your files, so your assistant does the editing and you review it like any other change.
This is the path most sellers should take. AI-assisted setup
2. Connect your own MCP client
Section titled “2. Connect your own MCP client”If you already work in an MCP client of your own, point it at the Monaiq MCP endpoint:
https://api.monaiq.com/mcp
The URL is the entire setup. There is no API key or session key to configure; the first request starts an OAuth sign-in and you confirm it with a one-time code sent to your email. You get the same tools as the plugin, in the client you already use.
3. The SDKs, by hand
Section titled “3. The SDKs, by hand”Both clients do the same work: authorize a credential, read the features it unlocks, and enforce them.
- .NET quickstart for the NuGet package, registered through dependency injection.
- Node and React quickstart for the npm package, in plain Node or behind a React provider.
Take this path when you want to see every call yourself, when your stack does not suit an assistant, or when you are fitting licensing into code that already exists and has its own shape.
Choosing
Section titled “Choosing”Start with the plugin if you have a coding assistant, because it does the catalog work as well as the code, and the catalog is the part that is easy to get subtly wrong. Use the MCP endpoint directly if you have already settled on a client. Go straight to an SDK page if you would rather write the calls yourself; nothing about the assisted paths is required, and they produce ordinary SDK code either way.
What none of these do
Section titled “What none of these do”Customer management, license CRUD, billing plan management, invoice operations and consumption analytics are not available over MCP. They are portal work, in the portal at monaiq.com, whichever integration path you take.
Every path other than MCP itself needs a credential from your account. See Credentials and keys.