by Make
Updated October 20, 2026
MCP100 verdict
Not currently recommended. First-party or well-evidenced implementation identity, meaningful task value, maintained setup evidence, and no material admission veto were found in reviewed sources.
MCP100 Assessment
Editorial verdict
Reviewed October 19, 2026
Task Fit
Mapped
Specialized workflows
Trust
Status warning
Shortlist evidence is sufficient for identity, setup and task value; authenticated runtime tool-schema measurement and exhaustive security certification remain out of scope.
Maintenance
Date unavailable
No dated repository or package update is currently stored.
Popularity
Signals unavailable
No independently comparable adoption metric is currently stored.
Evidence scope
No MCP-specific repository metric is stored
No MCP-specific package metric is stored
Stars observed October 20, 2026 · Downloads observed October 20, 2026
The current Make MCP is the Make-hosted cloud service documented at developers.make.com. The public `integromat/make-mcp-server` repository is explicitly labeled legacy and must not be used as current hosted-server adoption evidence.
The current Make MCP is hosted. `@makehq/mcp-server` belongs to the legacy local implementation and is excluded from current hosted-service adoption.
Publisher activity observed October 20, 2026
Current source snapshot
Source relationship: First-party MCP
Reviewed October 19, 2026
Evidence-backed setup
Choose your MCP client. A client connects to the MCP server; the language model is selected inside that client. Only stored, source-backed configurations are shown.
Transport not recorded
Complete client-specific setup, verification and removal are not documented in this reviewed source.
Publisher-documented setup is not the same as MCP100 execution testing. “MCP100 logic checked” means the stored configuration shape was reviewed, not that third-party MCP software was run.
Evidence checked 2026-10-20
Type-appropriate, source-backed setup for this mcp server profile.
{"url":"https://mcp.make.com","alternativeTokenUrl":"https://<MAKE_ZONE>/mcp"}Capability
Make MCP is Make’s hosted MCP server for running scenarios and managing Make account resources from AI clients. Management scopes can modify scenarios, connections, webhooks, data stores and organization resources; scenario runs can trigger downstream external actions. OAuth can restrict access to a specific Make organization, while MCP-token access is broader by token scope.
Current Make MCP tool surface is dynamic: scenario tools depend on configured on-demand scenarios, while management tools depend on scopes/plan.
Not measured yet
Estimated token footprint of the MCP tool schemas exposed to the agent.
https://mcp.make.com
Reviewed access
Related reviewed MCPs
Explore Tableau sites, workbooks, data sources, metadata, and governed analytics.
Choose this instead if
Choose tableau instead if business-intelligence discovery and analysis using authorized Tableau content.
Explore Tableau sites, workbooks, data sources, metadata, and governed analytics.
Read and update authorized Coda documents, pages, tables, and rows.
Choose this instead if
Choose coda instead if collaborative document and structured-table workflows in Coda.
Read and update authorized Coda documents, pages, tables, and rows.
Codebase knowledge graph for AI agents — 159 languages, sub-ms queries, 99% fewer tokens.
Choose this instead if
Choose Codebase Memory MCP instead if repository indexing, symbol search, call-path tracing, impact analysis, and architecture queries across many languages.
Recommended after reviewed 2026-09-25 admission dossier: all_current_selected_gates_pass.
Make is listed as First-party MCP in MCP100’s current evidence.
Current official resources:
Original product, capability, tool, and usage documentation from the MCP publisher. Installation sections appear under Install & Agents.
Title: Make MCP Server | MCP Server | Make Developer Hub
URL Source: https://developers.make.com/mcp-server
Markdown Content: ⌘Ctrl k
Make MCP server allows AI systems, such as large language models (LLMs), to run scenarios and manage your Make account. Model Context Protocol (MCP) is a communication standard between AI and external systems that enables safe interactions by defining endpoints and providing authentication.
AI systems like Claude and ChatGPT act as MCP clients of Make MCP server. The server gives them access to MCP tools that:
Make Skills are Markdown files with instructions on building scenarios, configuring modules, and connecting to Make MCP server or third-party services.
You can install them in MCP clients to connect to Make MCP server without setting up the connection manually and help clients reliably perform Make-specific tasks.
Make MCP server is a Make-hosted, cloud-based server that runs via stateless Streamable HTTP.
Connect it to MCP clients using OAuth or an API key. Alternatively, install Make Skills, which include connection details for Make MCP server.
Use the following URL:
The URL you use depends on whether your client supports adding the API key in Authorization headers.
API key in header
If you add the API key in an Authorization header, use the following URL:
Specify the API key in the Authorization header:
API key in URL
Use the following connection URL, and replace <MAKE_ZONE> and <API_KEY> with actual values:
MAKE_ZONE: The zone your organization is hosted in. For example, eu2.make.com.Optionally, append the following query parameter to the URL to set the tool name length:
?maxToolNameLength=<length>: Generated tool names have a maximum length of 56 characters by default, to be compatible with most AI systems. Use this parameter to set a different maximum length. The allowed range is 32 to 160 characters.Optionally, to control which scenarios are available as tools through your API key, see Scenarios as tools access control.
MCP tools are functions on Make MCP server that MCP clients call to interact with Make, such as running scenarios or updating data stores.
You can view the tools on Make MCP server in a few ways:
MCP client settings
In your MCP client's connector settings, select Make MCP server.
Tool names, and in some clients, descriptions and categories
MCP client command
In your MCP client, run its MCP command, for example /mcp in Claude Code, then select Make MCP server and a tool.
Tool names, descriptions, and schemas
MCP Inspector
In a terminal, run npx @modelcontextprotocol/inspector --cli https://<MAKE_ZONE>/mcp/v2 --transport http --header "Authorization: Bearer <API_KEY>".
Tool names, descriptions, and schemas
tools/list request
In your app or agent's code, send a tools/list request to Make MCP server, or use an SDK method, such as list_tools() (Python) or listTools() (TypeScript).
Tool names, descriptions, and schemas
Prompt in AI assistant
In your MCP client's chat, ask something like "What tools do you have from Make MCP server?"
Tool names and descriptions
Tool calls from MCP clients to Make MCP server have a timeout for returning output. Limits depend on the tool type and connection method.
Scenario run tools
https://mcp.make.com/v2 (OAuth): 25 secondshttps://<MAKE_ZONE>/mcp/u/<API_KEY>/v2 (API key): 40 secondsManagement tools
https://mcp.make.com/v2 (OAuth): 30 secondshttps://<MAKE_ZONE>/mcp/u/<API_KEY>/v2 (API key): 60 secondsRetrieve outputs after timeout
If a scenario run tool call times out, the scenario continues running in Make for up to 40 minutes. The timeout response includes an executionId that an MCP client can use to get the output after the scenario finishes.
Example response:
Select the scenarios:read scope to allow an MCP client to retrieve outputs after a timeout once a scenario run finishes.
When an MCP client uses a scenario as a tool, it refers to the scenario's inputs and outputs to know what data to send and what it gets back:
Write detailed scenario descriptions to help MCP clients understand what each scenario does and get more reliable results.
Last updated 3 hours ago
https://mcp.make.com/v2
https://<MAKE_ZONE>/mcp/v2
Authorization: Bearer <API_KEY>
https://<MAKE_ZONE>/mcp/u/<API_KEY>/v2
{
instruction: 'The Tool execution has started, but did not complete yet. Use a corresponding Tool for getting Execution Results to check for the result asynchronously.',
executionId: '4eb841b3fe3d48a5b2b59e2eed3f55be',
scenarioId: 1,
},