01 · Records and state owned
Active and on-demand scenarios; scenario executions and outputs; connections, webhooks, and data stores; teams and organizations; scoped scenario-run and account-management tools.
Make
Make
Make anchors visual automation because its hosted MCP turns active, on-demand scenarios into agent-callable operations and can also expose account-management tools for scenarios, connections, webhooks, data stores, teams, and organizations.
Automation, data & MCP bridgesSystem of orchestrationAgent-accessible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Discover eligible scenarios, inspect permitted scenario and account entities, and retrieve execution output when the relevant read scope is granted; management reads are available on paid plans.
03 · Actions and write paths
Run active or on-demand scenarios and, with paid-plan management tools and matching scopes, modify scenarios and related connections, webhooks, data stores, teams, or organizations.
04 · Authentication and permissions
Make-hosted MCP supports OAuth or an MCP token. OAuth selects an organization and scopes at consent; token scopes determine tools, and scenario discovery can be narrowed by mutually exclusive organization, team, or scenario URL filters.
05 · Monitoring, approval, and recovery
Scopes determine the tool catalog, but `mcp:use` on an MCP token exposes all active/on-demand scenarios across all Make organizations by default unless the URL is narrowed. BYO-UI should pin the narrowest organization/team/scenario filter and show the downstream scenario before every run.
06 · Limits and caveats
The MCP server is cloud-hosted by Make. Scenario-run tools are on all plans; management tools require a paid plan. Only active scenarios with on-demand scheduling become tools, OAuth run access covers every eligible scenario in the selected organization, team narrowing needs Teams+, and calls have transport-specific timeouts while scenarios may continue for up to 40 minutes.
Agent access
MCP support
Official MCP serverMake-hosted remote MCPCurrent documented cloud service
Support: Official MCP server
Read scope: List and inspect scoped scenarios and permitted account entities, then retrieve scenario outputs when `scenarios:read` or the corresponding OAuth scope is present.
Write scope: Invoke eligible scenarios and, on paid plans with management scopes, change scenarios, connections, webhooks, data stores, teams, and organizations.
Authentication: Make-hosted Streamable HTTP/SSE service authenticated through OAuth at `https://mcp.make.com` or a zone-specific MCP-token endpoint.
Approval boundary: Make documents scopes and scenario filtering, not an automatic human confirmation before a scenario run or account mutation. BYO-UI should require confirmation for scenarios with external side effects and for every management write, showing organization, scenario, inputs, and affected entities.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access4
Identity2
Governance3
Agent access4
UI extensibility3
Portability4
Observability4
Documentation5
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Make ships them.
Single-platform patterns
- Multi-system campaign operations console
- Marcom control plane
- Data-quality exception console
- Approved capability registry
Multi-platform compositions
- Make + systems of record: marcom control plane
- Make + systems of engagement + interface host or builder: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
7 recorded sources
MCPRepresentative source
https://developers.make.com/mcp-server ↗Hosted deployment, scenario runs, account management, scopes, plans, transport, and timeouts
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 22, 2026
Cloud deployment, tools, plan gates, scopes, discovery controls, and timeouts reviewed 2026-07-22
APISource inventory
https://developers.make.com/api-documentation ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://developers.make.com/ ↗First-party developer documentation or platform overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://www.make.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Webhooks / extensionsSource inventory
https://developers.make.com/custom-apps-documentation ↗First-party webhook, event, SDK, embedded-app, or extension documentation.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
MCP OAuthSource inventory
https://developers.make.com/mcp-server/connect-using-oauth ↗OAuth connection, organization binding, scopes, and plan-dependent team access
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 22, 2026
OAuth connection, organization binding, scopes, and plan-dependent team access reviewed from live first-party documentation on 2026-07-22.
MCP access controlSource inventory
https://developers.make.com/mcp-server/connect-using-mcp-token/scenarios-as-tools-access-control ↗MCP-token scenario discovery and URL-level access restriction
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 22, 2026
MCP-token scenario discovery and URL-level access restriction reviewed from live first-party documentation on 2026-07-22.
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.