How do I add an MCP server to Zapier?

1. Open the Zapier MCP settings page 2. Choose which app actions to expose 3. Copy the generated endpoint URL, which contains a secret 4. Paste that URL into your MCP client as a remote server

Where is the Zapier 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 Zapier run a local MCP server?

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

Which parts of the protocol does Zapier 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 Zapier also work as an MCP server?

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

Does Zapier 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.

Zapier

Automation platform that publishes its own MCP server exposing thousands of app actions, and can call other servers from a Zap.

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

How to add a server to Zapier

Zapier is mainly used the other way round. It hands you an endpoint that other clients consume, rather than consuming local servers itself. Treat the generated URL as a credential.

Open the Zapier MCP settings page
Choose which app actions to expose
Copy the generated endpoint URL, which contains a secret
Paste that URL into your MCP client as a remote server

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	Yes

Official Zapier MCP documentation

Frequently asked questions

How do I add an MCP server to Zapier?: 1. Open the Zapier MCP settings page 2. Choose which app actions to expose 3. Copy the generated endpoint URL, which contains a secret 4. Paste that URL into your MCP client as a remote server
Where is the Zapier 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 Zapier run a local MCP server?: No. Zapier cannot start a local process, so it only works with servers that publish an HTTP or SSE endpoint.
Which parts of the protocol does Zapier 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 Zapier also work as an MCP server?: Yes. Zapier publishes its own MCP server, so it can be called by other clients as well as calling servers itself.
Does Zapier need restarting after adding a server?: No, it picks up the change without a restart.
Is there anything specific to watch out for with Zapier?: Zapier is mainly used the other way round. It hands you an endpoint that other clients consume, rather than consuming local servers itself. Treat the generated URL as a credential.
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