Skip to content

AI-assisted setup

This page is for you if an AI assistant writes your code. It installs the Monaiq plugin into Claude Code, GitHub Copilot or Codex, signs you in, and tells you what the tools it brings can and cannot do.

The plugin is published from the GitHub repository Sidub-Inc/Monaiq.AI.

Run these two commands in Claude Code:

/plugin marketplace add Sidub-Inc/Monaiq.AI
/plugin install monaiq@monaiq

The first adds the Monaiq marketplace, the second installs the plugin from it.

Add the repository Sidub-Inc/Monaiq.AI as an agent plugin source in VS Code. Copilot reads the plugin.json at the repository root. See the Copilot agent plugins guide.

Add the repository Sidub-Inc/Monaiq.AI as a plugin in the Codex CLI. Codex reads .codex-plugin/plugin.json and .agents/plugins/marketplace.json. See the Codex documentation. A Codex install carries the skills and the MCP server, not the monaiq agent.

There is nothing to configure after installing. The first tool call answers with a challenge, your client starts an OAuth sign-in, and you confirm it with a one-time passcode sent to your email address.

Getting oriented. getting_started explains the business domain and how the rest of the tools fit together. It is the sensible first call in a new project.

Your account. profile views and manages your seller profile, retrieves your credentials (the account API key only for an owner), reads and accepts terms, sets your billing rules, and registers your customer sign-in. Viewing the profile also tells the agent whether you can sell: your plan, where your payouts stand (how many things are still needed, and by when), and anything that needs you. The agent sends you to the one page that moves it on, the Start selling steps while you are getting set up and the Payouts page after; it never sets up payouts for you. account lists the accounts you belong to and switches the one the tools act as. rotate_api_key regenerates your API key; only an owner of the account can run it.

Your catalog. product, product_feature, offering and feature_offering create, read, update and delete the four things a catalog is made of: the product a license unlocks, the features inside it, the offering a customer buys, and the features attached to that offering. A create mints its own id; an id you supply is ignored.

Licenses and seats are not assistant tools. Your backend manages them through the HTTP management API, and your customers on their license page, so every change that moves money is confirmed by a person.

The integration. implement_base covers the base wiring, implement_product_feature covers checking a single feature, and implement_purchase_flow covers an embedded purchase flow so customers can buy from inside your product. These three return guidance and snippets; they do not edit your files. Your assistant reads them and writes the code, which means you review a normal diff.

Supporting tools. get_platform_manifest returns the full JSON manifest for a supported platform. provision_api_key_config gives you the exact commands and file edits that plumb your API key into a project. fetch_step_resources retrieves the resources a step refers to, and monaiq_journal keeps the implementation journal across a longer piece of work.

The tools write your catalog directly, so check the result in the portal: products shows what now exists, each product with its features and offerings, and an offering stays in Draft until you publish it.

The code the assistant writes is ordinary SDK code. If you want to read the reference for it yourself, see the .NET quickstart or the JavaScript SDK quickstart.

The same tools are available to any MCP client, without the plugin’s skills. See Connect over MCP.