MCP — AI clients
Let Claude Desktop, Cursor, or any MCP client build and edit workflows.
MadMax exposes the same tool surface the in-canvas assistant uses over the Model Context Protocol, so external AI clients can list your workflows, add steps, wire edges, verify, and activate — from outside the browser.
Connect a client
- Mint a token in Settings → developer (the same
mmx_token the REST API uses; pinned to one workspace). - Copy the ready-made config snippet for your client from that same tab — Claude Desktop, Cursor, and a generic template are provided.
- The endpoint is
POST /mcpwith your token as the bearer.
Every tool call runs as you, in the token's workspace, under your permissions. Read-scope tokens can only look; the build scope unlocks mutations.
What clients can do
The tool surface covers discovery (list workflows, step templates, searchable integration operations), graph editing (add / update / remove / connect steps), lifecycle (activate, deactivate, run), and debugging (recent runs with per-step input and output).
One token, two doors
The REST API and MCP share the token system — mint once, use either. Requests from both surfaces land in the same per-token activity log in Settings → developer.