speaks licensing.
Monaiq exposes a full MCP server — the Model Context Protocol that powers AI agents in VS Code, Cursor, Windsurf, and more. AI assistants can create products, features and offerings, manage your profile and API key, and hand back the integration code for your project.
Why MCP?
The Model Context Protocol is an open standard that lets AI agents call external tools — like function calling, but standardized across every IDE and AI assistant. When your tool speaks MCP, any compatible agent can discover it, understand what it does, and invoke it on behalf of the user.
Why does this matter for licensing? Developers spend most of their day in AI-assisted IDEs. If the licensing platform speaks MCP, the AI assistant becomes the interface. “Add a free trial tier” becomes a one-sentence instruction, not 15 minutes in a dashboard. “Write the feature check for this endpoint” comes back as code for your own project, in the same conversation where you’re writing it. The AI handles the tool calls, you handle the product decisions.
How It Works
Three steps from install to shipping licensed software.
Connect
Install the Monaiq MCP server in your AI IDE — one click for VS Code, Cursor, and more. On first use your assistant signs you in with an email one-time passcode. No API key to configure.
Converse
Tell your AI assistant what you need. “Create a product called ‘Pro Plan’ with feature gating for analytics and export.” The assistant translates natural language into MCP tool calls.
Ship
The tools hand back SDK code for your project and your real catalog. Your assistant writes it in, and you review the diff like any other change.
What your AI agent can do
What the tools cover — and what stays in the portal on purpose.
Products & Features
Create and update products and their features — access, rate limit or allowance — in natural language.
Offerings & Pricing
Create offerings with a price, billing schedule and category, attach features to each, and publish them when you are ready.
Profile & Credentials
Review your seller profile, accept terms, retrieve your credentials, rotate your API key, and switch which of your accounts the tools act as.
Purchase Flow
Guidance for selling from inside your app — the buyer signs in and pays as themselves — plus the exact commands to plumb a credential into your project.
Stays in the Portal
Licenses, seats, customers, invoices and usage analytics are not MCP tools. That work happens in the portal and your backend, where a change that moves money is confirmed by a person.
Integration Guidance
Base wiring and a feature check for .NET or React, built from your real catalog. The tools return guidance and snippets; your assistant does the editing.
Install in One Click
Add Monaiq to your AI-powered IDE and start building.
Any other MCP client
Windsurf, Claude Desktop, or anything MCP-capable: paste this config. The URL is the entire setup — your assistant discovers Monaiq's OAuth sign-in and prompts you for an email one-time passcode.
{
"mcpServers": {
"monaiq": {
"url": "https://api.monaiq.com/mcp"
}
}
}Using Claude Code, GitHub Copilot, or Codex?
Install the full Monaiq AI plugin instead — it bundles this MCP server with skills that guide your assistant through pricing design and SDK integration. In Claude Code:
/plugin marketplace add Sidub-Inc/Monaiq.AI
/plugin install monaiq@monaiqCopilot and Codex install from the same repository — the get-started guide has the exact steps for each assistant.
Connection details, OAuth flow, and the full tool list are in the MCP integration docs.
Want the full story behind why we built an MCP server and what it means for the future of developer tools?
Why We Built an MCP Server →