Make MCP Server

Make's own MCP server, hosted by Make, connects your agent to your Make account. Your agent can run your active and on-demand scenarios as tools, and on paid plans it can also view and change your scenarios and what they use, such as connections, webhooks and data stores, plus your teams and organizations. What you can do with it - Run your active and on-demand scenarios, using the inputs and outputs you set up in Make - Find the right Make apps and modules for a job, and read their documentation - Build and deploy new scenarios from blueprints, with each module's setup checked first - List your connections and start sign-in for new ones - Create webhooks for instant triggers, data stores and data structures - View and change teams and organizations How it connects Make hosts it at mcp.make.com, over Streamable HTTP. With OAuth, Make's consent screen asks you to pick an organization and the scopes it gets, and those scopes decide which tools your agent sees. Make's current docs give https://mcp.make.com/v2 for OAuth, with https://mcp.make.com/claude for Claude Code and https://mcp.make.com/openai for ChatGPT; in Claude, Make is a built-in connector. You can use a Make API key instead, with your organization's zone in the address (for example https://eu2.make.com/mcp/v2) and the key in an Authorization header. Good to know - Scenario run tools work on every plan; the management tools need a paid plan. - The "Run your scenarios" scope gives access to all on-demand and active scenarios in the organization. To narrow it, a Teams plan or higher lets you give people accounts limited to specific teams. - If a scenario takes longer than the tool call's time limit (25 seconds over OAuth), it keeps running in Make for up to 40 minutes and your agent can fetch the result afterwards. - Make Skills, Make's skills for Claude, teach your agent how to build scenarios and configure modules with this server.