Make MCP

Make is a visual automation platform where you build scenarios that chain app integrations together. Its MCP server inverts the usual direction of that relationship: instead of a scenario calling an AI model, the model calls the scenario. Any scenario you want exposed must be active and set to on demand scheduling, and it then appears to the client as a callable tool that takes structured inputs and returns structured output. Access runs through an MCP token generated in the API and MCP access area of a Make profile, which produces the server URL a client connects to, and access control is applied per scenario so you choose exactly which automations an agent may trigger. The payoff is reach. Anything already connected inside Make, from CRMs and spreadsheets to internal HTTP endpoints, becomes callable from an assistant without writing and hosting a bespoke MCP server for each system. Make offers a cloud endpoint plus a legacy local server for self managed setups, and separately an MCP client module that lets a scenario call out to external MCP servers, which is the mirror image of the same idea. The design point most people get wrong is inputs. A scenario originally built around a webhook payload often needs a cleaner, better named input schema before a model can call it reliably, so treat an exposed scenario as an API you deliberately design rather than one you inherit.