Connect over MCP

This page gives you the Monaiq MCP endpoint, explains how signing in works, and summarises what the tools do.

The endpoint

https://api.monaiq.com/mcp

The URL is the entire setup. Point your MCP client at it and you are done: there is no API key to paste, no session key, and no configuration file to fill in beyond the address itself. None of the tools take a credential as a parameter either.

Note

That address is the only one. Older Monaiq endpoints that appeared in earlier material no longer answer, so if you have one saved from before, replace it with this.

Transport and protocol

The endpoint speaks the MCP Streamable HTTP transport. Every JSON-RPC message travels as an HTTP POST to the endpoint above; responses arrive as JSON or as a short event-stream your client already understands. Where a client configuration asks for a transport type, use http (some clients call it streamable_http). GET on the endpoint answers 405 Method Not Allowed — the server offers no server-initiated stream — and nothing is served on any path beneath it.

Details your client handles for you, documented for the curious:

• Protocol version — negotiated during initialize; the server currently answers 2025-06-18, and also accepts the earlier 2025-03-26 and 2024-11-05 revisions. If you ask for a version it does not know, it answers with the version it speaks and your client decides. On requests after initialize, clients send the negotiated version in the MCP-Protocol-Version header.
• Sessions — initialize returns an Mcp-Session-Id header your client echoes on later requests. The value is self-contained: the server keeps no session state behind it, any request works on any server instance, and there is nothing to resume or tear down — DELETE answers 405 because termination is unnecessary.

Signing in

Authentication is MCP-spec OAuth 2.1, and your client drives all of it:

1. The first request answers 401 with a WWW-Authenticate header pointing at https://api.monaiq.com/.well-known/oauth-protected-resource.
2. Your client reads that document and starts the OAuth flow it describes.
3. You sign in with a one-time passcode sent to your email address.

From then on the client holds the token and you work in tools. The code that arrives by email is the only thing you have to supply by hand.

What the tools cover

getting_started orients you: it explains the business domain and how the rest of the tools fit together.

profile views and manages your seller profile, retrieves your credentials, and reads and accepts terms. rotate_api_key regenerates your API key, and the old key stops authenticating immediately.

product, product_feature, offering and feature_offering are the catalog: creating, reading, updating and deleting the product a license unlocks, the features inside it, the offering a customer buys, and the features attached to that offering.

Licenses, seats and license codes are not MCP tools: your backend manages them through the HTTP management API, where a change that moves money is confirmed by your own code.

implement_base, implement_product_feature and implement_purchase_flow return guidance and snippets for the integration itself: base wiring, a feature check, and an embedded purchase flow. They do not edit files. get_platform_manifest returns the full JSON manifest for a supported platform, provision_api_key_config gives the exact commands and file edits to plumb your API key into a project, fetch_step_resources retrieves the resources a step refers to, and monaiq_journal keeps an implementation journal across longer work.

MCP tools reference lists all of them in one table.

What is not available over MCP

Caution

These are not exposed as tools:

• customer management
• licenses, seats and license codes
• invoice operations
• consumption analytics

Do that work in the portal at monaiq.com.

In Claude Code

Claude Code users can install the Monaiq plugin instead of configuring the endpoint by hand. It is two commands, and it packages the same tools: see AI-assisted setup.

After the tools

The tools set up your catalog and hand you the integration guidance; the code still runs against the SDKs. See the .NET quickstart or the Node and React quickstart, and Credentials and keys for the key that code will need.