---
title: "Make Hosted MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/make/
description: "Run on-demand scenarios and manage authorized Make scenarios, connections and organization resources."
---

# Make Hosted MCP: review, setup & limitations · Undominated.ai

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

[← Explore all mcp servers](/mcp-servers/)

WORKFLOW AUTOMATION / Make

# Make Hosted MCP

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

 [See setup guidance ↓](#setup)[Original source ↗](https://developers.make.com/mcp-server)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 2 linked sources
 Publisher Make
 Licence Not established
 [Read what was—and wasn’t—checked ↓](#review)

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

 [Make · upstream description ↗](https://developers.make.com/mcp-server) Our analysis follows below.

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.

### A good fit for

 - Run on-demand scenarios and manage authorized Make scenarios, connections and organization resources.
- 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.

### Weigh up before choosing

 - 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.
- Hosted implementation and deployment revision were not inspected; public connection documentation was reviewed.

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 ↗](https://developers.make.com/mcp-server)
 - 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.
- 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.

### Compatibility

Remote MCP clients supporting the publisher authentication flow.

### Transports

Streamable HTTP

### Hosted account authorization

 - Scopes determine available tools; scenario executions can perform whatever actions their connected apps permit, and management tools can alter account resources.

### Cost model

Publisher service entitlements, API usage and infrastructure charges apply where applicable; the MCP source licence does not include external services.

04 / FOLLOW THE EVIDENCE

## The source trail.

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

 - [Pinned publisher README and migration notices ↗](https://github.com/integromat/make-mcp-server/blob/f436799ef010276c18ea98ed0ed0a45dc748608b/README.md) Checked 2026-10-14 https://github.com/integromat/make-mcp-server/blob/f436799ef010276c18ea98ed0ed0a45dc748608b/README.md Supports: description, setup, capabilities, review, limitations
- [Publisher connection and operating guide ↗](https://developers.make.com/mcp-server) Checked 2026-10-14 https://developers.make.com/mcp-server Supports: description, install, access, limitations, bestFor, review

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### n8n Instance MCP ↗ Exposes n8n workflow discovery, execution and authoring through an instance endpoint with user permissions and workflow access controls.](/mcp-servers/n8n-instance/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
