Make.com has an MCP endpoint now. The auth token goes in the URL — and 3 other walls the docs skip
Make.com has introduced a new MCP endpoint, but integrating it with AI agents presents several undocumented challenges. Developers must navigate issues such as Cloudflare's User-Agent blocking, the need for a `teamId` instead of `organizationId` to list scenarios, and handling unescaped newline characters within JSON blueprints. Additionally, the MCP endpoint requires the authentication token to be embedded directly in the URL, rather than in a standard `Authorization: Bearer` header, posing a security concern for sensitive credentials. AI
IMPACT Developers integrating AI agents with Make.com must account for specific API quirks and security considerations.