Skip to main content
The only real difference between AI clients is how they authenticate: OAuth from inside the client, or a connection token.

What a Zapier MCP connection is

A Zapier MCP connection links one AI client to one MCP server on your Zapier account. The server holds the actions your client can call, and runs each call through your existing Zapier app connections. Every client connects to the same endpoint:
Zapier holds the app credentials, so your client never handles a third-party API key.

Supported transport

Zapier MCP supports the Model Context Protocol over Streamable HTTP only. A client that can only use SSE (Server-Sent Events) cannot connect.
If your client offers a transport choice, select Streamable HTTP. If it was configured against an SSE endpoint, update it to the URL above.

Authentication methods

Your client decides which path applies.

OAuth

The client registers Zapier as an MCP server and sends you through a Zapier sign-in. Zapier names the server after the client and auto-provisions actions from the apps already connected to your Zapier account. You do not manage a credential: the client stores and refreshes the OAuth token. Revoke the connection from the client or from mcp.zapier.com. If your organization manages your AI client, an admin or owner may need to approve the Zapier connector first. Each client’s setup page says whether that applies.

Connection token

You create the server at mcp.zapier.com, generate a token, and give it to your client. The token is long-lived, tied to that one server, and grants whoever holds it the ability to run the server’s tools and read the data they return. Your client supports one of two forms: Prefer the header: a URL is more likely to end up in a log, a shell history, or a committed config file.
Treat a connection token like a password. Store it in an environment variable or a secret manager, and give each user their own server and token rather than sharing one.
A token is shown once, so store it straight away. Regenerating a token immediately invalidates the previous one, and any client still using it stops working until you update its configuration. For the steps on this path, check Connect any other client, Python, or TypeScript.

One server per client

Each AI client gets its own MCP server: one for Cursor, one for Claude, one for ChatGPT. You can have several, but only one per named client. A server has no limit on actions or tool calls. The only limit is the task allowance on your Zapier plan.

Next steps

Quickstart

Connect your client and run your first tool call end to end.

How tools work

How dynamic tool discovery works, and what each meta-tool does.

Security

Access control, compliance, and audit logging.
Last modified on August 26, 2026