01 · Records and state owned
Run scenarios and manage approved Make account contents; scenarios can be exposed as callable tools
Make
Make
Curated anchor platform in visual automation and orchestration with material relevance to the Marcom operating stack and a first-party developer surface.
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
Run scenarios and manage approved Make account contents; scenarios can be exposed as callable tools
03 · Actions and write paths
Make's first-party MCP/agent surface includes state-changing tools in the documented capability area: Run scenarios and manage approved Make account contents; scenarios can be exposed as callable tools. The audit did not enumerate every mutation; verify the current tool catalog and require explicit confirmation for consequential actions.
04 · Authentication and permissions
Official Make docs confirm OAuth or scoped MCP-token access; legacy local/cloud pages should be replaced with current canonical docs. Official Make docs confirm OAuth or scoped MCP-token access; legacy local/cloud pages should be replaced with current canonical docs.
05 · Monitoring, approval, and recovery
Official Make docs confirm OAuth or scoped MCP-token access; legacy local/cloud pages should be replaced with current canonical docs. Official Make docs confirm OAuth or scoped MCP-token access; legacy local/cloud pages should be replaced with current canonical docs.
06 · Gaps and implementation limits
Official Make docs confirm OAuth or scoped MCP-token access; legacy local/cloud pages should be replaced with current canonical docs.
Agent access
MCP and adjacent posture
Verified first-party provider MCPMake-hosted remote MCPCurrent service
Role: provider
Read scope: Run scenarios and manage approved Make account contents; scenarios can be exposed as callable tools
Write scope: State-changing tools are present in the documented scope; review the official tool catalog and require confirmation for consequential actions.
Authentication: Official Make docs confirm OAuth or scoped MCP-token access; legacy local/cloud pages should be replaced with current canonical docs.
Approval boundary: Official Make docs confirm OAuth or scoped MCP-token access; legacy local/cloud pages should be replaced with current canonical docs.
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 interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that Make ships these experiences.
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.
5 recorded sources
MCPRepresentative source
https://developers.make.com/mcp-server ↗Official Make docs confirm OAuth or scoped MCP-token access; legacy local/cloud pages should be replaced with current canonical docs.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
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.
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.
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.
Verified fact
Tied to the representative first-party source or targeted access review.
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.