Make MCP
Make
Streamable HTTP (stateless recommended); SSE and stateful Streamable HTTP are also documentedTool names not enumerated0
About Make MCP
Make’s hosted MCP lets clients run active Make scenarios as callable tools and, with appropriate paid-plan management scopes, manage Make organization resources.
What you can use it for
- Run active on-demand scenarios exposed as tools.
- View and manage scenarios, teams, connections, webhooks and data stores when permitted.
- Create restricted toolboxes containing selected scenarios.
Connection and setup
- Hosting
- remote
- Transport
- Streamable HTTP (stateless recommended); SSE and stateful Streamable HTTP are also documented
- Endpoint
- https://mcp.make.com
- Authentication
- OAuth or Make MCP token; scopes control scenario-run and organization-management access.
Requirements
- Make account and at least one active on-demand scenario for scenario tools
- Paid Make plan for management scopes; scenario-run scopes are available on all plans
- MCP client with a supported remote HTTP transport and OAuth or token flow
Setup steps
- Activate the Make scenario(s) to expose and configure them for on-demand scheduling; define meaningful inputs, outputs, and descriptions.
- In the Make profile, create an MCP token if not using OAuth, select its scopes, and copy the token securely.
- For OAuth, configure https://mcp.make.com and finish browser authorization. For MCP-token mode, follow the organization-zone URL/header format documented by Make.
- Restrict access to only the scenarios and management scopes required. Refresh the tool list in the client and verify with a harmless read operation before running workflows.
Tools
No individual tool names are documented in the reviewed sources.
Current Make docs require an authenticated tools/list request to obtain tool names and schemas. Scenario tools are generated from the user’s active scenarios; management tools vary by OAuth/API scopes and plan, so no universal fixed IDs are published in reviewed docs.
Limitations and notes
- Scenario-run scopes are available on all plans; management scopes require a paid plan.
- OAuth is required to restrict connection access to one Make organization.
Original sources
- official or registry primary documentation
Official product reference describes scenarios as tools and use across connected apps.
- official or registry primary documentation
Official guide explains selecting scenarios, API key authorization, and per-tool access.
- official publisher documentation
Official docs describe scenario-run scopes, paid-plan management scopes, and toolbox-based custom tool exposure; no fixed tool list applies.
- official crawl4ai tool inventory audit
Crawl4AI 0.9.5 fetched the selected documentation page. No exact MCP tool identifiers were present in the captured page content; where attempted, the hosted tools/list endpoint required authorization.
- official crawl4ai tool inventory audit
Publisher states MCP toolbox tools are customer-selected active on-demand scenarios with custom labels; names are user/workspace-specific and no universal identifiers exist.
Documentation checked 2026-10-28T20:30:00.000Z. Connection has not been runtime tested.
