← Explore all mcp servers

WORKFLOW AUTOMATION / Make

Make Hosted MCP

Run on-demand scenarios and manage authorized Make scenarios, connections and organization resources.

“Run on-demand scenarios and manage authorized Make scenarios, connections and organization resources.”

01 / THE REASONING

Why this made the selection.

  • Run on-demand scenarios and manage authorized Make scenarios, connections and organization resources.
  • The setup documentation makes this operating boundary explicit: Scopes determine available tools; scenario executions can perform whatever actions their connected apps permit, and management tools can alter account resources.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • README.md
  • https://developers.make.com/mcp-server

Our findings

  • Scopes determine available tools; scenario executions can perform whatever actions their connected apps permit, and management tools can alter account resources.
  • The local repository is legacy. A client timeout does not stop the scenario; retain executionId and retrieve completion with scenarios:read instead of blindly running it again.

Not established by this review

  • No server installation, authentication, live tool execution or isolation test was performed.
  • Hosted implementation and deployment revision were not inspected; public connection documentation was reviewed.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗
  1. Connect https://mcp.make.com using OAuth, select the needed scopes, and expose only intended active on-demand scenarios. Token authentication instead uses the documented regional zone endpoint and MCP token.
  2. Verify the connected account, available tools and target resource before authorizing mutations.

Before you start

  • A compatible remote HTTP MCP client.
  • Scopes determine available tools; scenario executions can perform whatever actions their connected apps permit, and management tools can alter account resources.

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/integromat/make-mcp-server/blob/f436799ef010276c18ea98ed0ed0a45dc748608b/README.md

    Supports: description, setup, capabilities, review, limitations

  2. https://developers.make.com/mcp-server

    Supports: description, install, access, limitations, bestFor, review

Evidence & Ask