How do I add an MCP server to Make?

1. Open your Make profile and create an API token with MCP scope 2. Copy the MCP server URL for your zone 3. Add the URL and token to your client as a remote server 4. Mark the scenarios you want exposed as available to MCP

Where is the Make MCP configuration stored?

There is no file to edit. Servers are added through the interface, and any API key is stored in the platform's own credential store.

Can Make run a local MCP server?

No. Make cannot start a local process, so it only works with servers that publish an HTTP or SSE endpoint.

Which parts of the protocol does Make not support?

It does not implement resources, prompts, sampling or elicitation. A server whose value is mostly in those features will feel incomplete here.

Does Make also work as an MCP server?

Yes. Make publishes its own MCP server, so it can be called by other clients as well as calling servers itself.

Does Make need restarting after adding a server?

No, it picks up the change without a restart.

When was this setup information last checked?

These details were verified on 2026-07-15. Clients change their configuration format from time to time, so check the official documentation if something does not work.

Make

Visual automation platform. Publishes an MCP server so an agent can trigger scenarios, and can call remote servers from a scenario.

Automation platform also publishes a server verified 2026-07-15

How to add a server to Make

Only scenarios explicitly flagged for MCP are exposed. Local stdio servers cannot be used from Make.

Open your Make profile and create an API token with MCP scope
Copy the MCP server URL for your zone
Add the URL and token to your client as a remote server
Mark the scenarios you want exposed as available to MCP

Where the configuration lives

Configured in the interface, not in a file.

Local server configuration

Not supported by this client.

Hosted server configuration

Not supported by this client.

Placeholders such as {{name}}, {{command}}, {{args}} and {{url}} are filled from each server's package or endpoint data.

Protocol support

Support is uneven across clients. A server that only exposes prompts is of no use in a client that does not implement them.

Transports
Transport	Supported
stdio	No
Streamable HTTP	Yes
SSE	Yes

Features
Feature	Supported
Tools	Yes
Resources	No
Prompts	No
Sampling	No
Roots	No
Elicitation	No
OAuth	No

Official Make MCP documentation

Frequently asked questions

How do I add an MCP server to Make?: 1. Open your Make profile and create an API token with MCP scope 2. Copy the MCP server URL for your zone 3. Add the URL and token to your client as a remote server 4. Mark the scenarios you want exposed as available to MCP
Where is the Make MCP configuration stored?: There is no file to edit. Servers are added through the interface, and any API key is stored in the platform's own credential store.
Can Make run a local MCP server?: No. Make cannot start a local process, so it only works with servers that publish an HTTP or SSE endpoint.
Which parts of the protocol does Make not support?: It does not implement resources, prompts, sampling or elicitation. A server whose value is mostly in those features will feel incomplete here.
Does Make also work as an MCP server?: Yes. Make publishes its own MCP server, so it can be called by other clients as well as calling servers itself.
Does Make need restarting after adding a server?: No, it picks up the change without a restart.
Is there anything specific to watch out for with Make?: Only scenarios explicitly flagged for MCP are exposed. Local stdio servers cannot be used from Make.
When was this setup information last checked?: These details were verified on 2026-07-15. Clients change their configuration format from time to time, so check the official documentation if something does not work.

Other clients

Claude Desktop Claude Code Cursor Visual Studio Code Cline Windsurf