Overview
Minimo is exposed as an MCP server (Model Context Protocol). Once connected, your AI agent can read and act on your workspace — contacts, segments, email & WhatsApp templates, campaigns, automations and connection status — through Mo’s tools. The endpoint ishttps://api.minimo.it/mcp (Streamable HTTP).
Most clients — Claude, ChatGPT, Cursor — don’t need an API key: point them at the URL and they discover the Minimo sign-in automatically (OAuth). You just click Authorize.
For scripts, automations and clients that can’t run a sign-in flow, use an API key: an mn-… key with the MCP (AI agent) permission (mcp:invoke), sent as a Bearer token in the Authorization header.
Get an API key
1
From the dashboard (fastest)
In Settings → Mo & MCP, the “Use Mo everywhere” card shows your key already generated — copy it straight
from the input. It’s scoped to MCP only and valid for 1 year.
2
Or from Developer settings
Go to Developer → API keys, create a new key and select the MCP (AI agent) permission.
3
Copy it immediately
The key is shown once. Store it securely — you won’t be able to see it again.
Claude (claude.ai)
1
Add the custom connector
Open Claude → Settings → Connectors and click Add custom connector.
Name it
Minimo and set the URL to https://api.minimo.it/mcp.2
Authorize
Press Add, then Connect — a Minimo window opens; click Authorize. No key to copy.
Claude Code (CLI)
Cursor
Add Minimo to.cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
ChatGPT
Open ChatGPT → Settings → Apps & Connectors, enable Developer mode (Plus/Pro/Enterprise), click Add connector with the Minimo MCP URL, set authentication to OAuth and click Authorize in the Minimo window.Try it
Paste this into your connected agent — it’s read-only and proves the connection end-to-end:Troubleshooting
- 401 Unauthorized — the key is missing the
mcp:invokepermission, expired, or malformed. Mint a fresh one from the dashboard card. - Connector shows no tools — make sure the URL is exactly
https://api.minimo.it/mcp(no/v1prefix) and the transport is HTTP (not SSE). - Wrong workspace — keys are company-scoped: the agent acts on the company the key was created in. Ask the agent which workspace it’s connected to, or reconnect from Settings → Mo & MCP.