Make

Name: Make MCP Server
Availability: InStock
Author: Make

Productivity67 tools

Run Make scenarios and manage your Make account from an AI assistant. 67 management tools plus your own scenarios as callable tools, OAuth sign-in, streamable HTTP.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 18 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Make via MCP

https://mcp.make.com

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Make Tools & Capabilities (67)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

The connector can cause side effects nothing in its tool list describes. scenarios_run executes an automation you built, and that automation can reach every app you have connected to Make. Sending mail, writing to a CRM, moving money through a payments integration — all of it sits behind one generic-looking tool name. This is a materially larger blast radius than a connector that only touches its own vendor's data, and Make's documentation does not describe a confirmation step before a run.
scenarios_activate re-arms a schedule. Activating a scenario is not a one-shot action; the scenario may then run on its own afterwards. Make requires scenarios to be active before they are discoverable as tools, so activation is part of the normal flow rather than an edge case.
Runs spend operations, and the guard rail is a pause, not a warning. Make's own example puts a single run of a modest four-module scenario at 31 operations. When the organization or team hits its operations or data transfer limit, Make returns 429/IM310 and refuses the run — the same pause that stops your scheduled automations. Make also documents that the run endpoint is exempt from the organization request limits, so those are no brake.
Neither well-known document publishes scopes. The RFC 9728 protected-resource descriptor at https://mcp.make.com/.well-known/oauth-protected-resource returned HTTP 200 on 2026-08-18 with resource, authorization_servers and bearer_methods_supported and no scopes_supported field. The authorization server's own metadata returned HTTP 200 and also omits scopes_supported. We therefore cannot state a machine-readable scope list. The three consent options named above come from Make's documentation, not from a wire observation.
OAuth cannot be narrowed below the organization. Make documents team-level and scenario-level restriction only for MCP token connections. On this connector, choosing an organization at the consent screen is the finest available filter. Make's suggested workaround is a Teams-plan user account limited to specific teams.
Management tools require a paid plan. A Free-plan connection is scenario-run only, so most of the 67 tools on this page will not appear.
The 67 names are a listing, not a vendor-verified inventory. Make publishes no tool reference for the MCP server, so we could not diff the directory's names against the vendor's own list. The prose descriptions in Make's docs match the groups, which is corroboration rather than confirmation.
The tool list varies by account. Your scenarios become tools too, so the list a client sees is 67 management tools plus your own scenarios. Nobody's list matches this page exactly.
We read no schemas or annotations. Our checks were anonymous protocol requests that returned an authentication challenge, plus reads of two public well-known documents. We never signed in, never called a tool and never ran a scenario. Everything about tool behaviour here comes from Make's documentation or the directory listing.

Frequently asked questions

What does the Make MCP server let an AI assistant actually do?

Two different things. It runs your Make scenarios as callable tools, and it manages your Make account through 67 tools covering scenarios, connections, data stores, webhooks, teams and organizations. Make's documentation describes it as letting clients run scenarios, check data stores, or invite members to an organization.

Which Make plan do you need for the MCP server?

Any plan runs scenarios; management needs a paid plan. Make's help centre states that users on all plans can use scenario run scopes, and those on paid plans can use management scopes. So a Free account connects and triggers scenarios, but the 67 account-management tools stay unavailable until you upgrade.

Does running a Make scenario from an AI assistant consume operations?

Yes. A scenario run through the connector is a real run and consumes operations exactly as any other run does. Make's scenarios API states the run is refused with a 429 and code IM310 when the organization or team is paused for exceeding an operations or data transfer limit, the same way Make stops scheduling.

Why does the Make MCP endpoint have no path after the hostname?

Because that is the endpoint Make publishes. The OAuth connection URL is the bare host, and appending the conventional /mcp path returns HTTP 404. We probed both on 2026-08-18: the bare host answers with a 401 authentication challenge, which is the correct endpoint asking you to sign in.

Which scenarios become tools for the AI assistant?

Only scenarios that are active and scheduled on demand. Make's help centre lists both conditions as requirements for a scenario to be discoverable by MCP clients. You also need scenario inputs and outputs configured, plus a scenario description, which is what the assistant reads to decide when to call it.

Can you limit the Make MCP connection to one team or one scenario?

Only on the MCP token connection, not on OAuth. Make documents organizationId, teamId and scenarioId query parameters that narrow which scenarios become tools, and states the levels are mutually exclusive. OAuth lets you pick one organization at consent, and Make notes a Teams plan or higher allows team-scoped user accounts.

How long can a Make MCP tool call run before it times out?

25 seconds for a scenario run over OAuth, and 30 seconds for a management tool. Make documents that a timed-out scenario keeps running for up to 40 minutes and returns an executionId you can use to fetch the result later. Token-based connections get longer limits, up to 5 minutes 20 seconds.