How to connect the Zapier MCP server

Before you start

• A Zapier account. With OAuth clients you can create one during sign-in. docs.zapier.com/mcpdocs.zapier.com/mcp
• Zapier MCP runs on your existing Zapier plan with no separate MCP billing. Each successful tool call uses two tasks from your plan's task allowance; failed calls use none. docs.zapier.com/mcp
• If your organization manages your MCP client, an admin or owner may need to approve the Zapier connector before members can add it. On Claude Team and Enterprise plans an Owner or Primary Owner must enable Zapier in Organization settings first. docs.zapier.com/mcpdocs.zapier.com/mcp
• An MCP client that supports Streamable HTTP. Clients that can only use SSE cannot connect. docs.zapier.com/mcp

Authentication

Your client → Zapier MCP

OAuth sign-in, handled by your MCP client. docs.zapier.com/mcpmodelcontextprotocol.io/specification

Zapier MCP → Zapier API

The server uses credentials the server manages. docs.zapier.com/mcp

Steps

1. Open Zapier's MCP quickstart and pick your client's setup page

   docs.zapier.com/mcp/get-started/quickstart
2. Add the Zapier MCP server to your client

   Add https://mcp.zapier.com/api/v1/connect as a remote MCP server that uses the Streamable HTTP transport (often labelled "http"). You don't need to create a server at mcp.zapier.com first: on sign-in Zapier connects the client to your default server and creates one if needed. Zapier also publishes a Claude connector, a one-click VS Code install, a Cursor marketplace plugin and a Claude Code plugin.

   docs.zapier.com/mcpdocs.zapier.com/mcpregistry.modelcontextprotocol.io/v0.1
3. Sign in to Zapier and allow access in the authorization window
   docs.zapier.com/mcpdocs.zapier.com/mcp
4. If your client isn't on Zapier's supported list or can't use OAuth, use a connection token

   Create a server at mcp.zapier.com (choose Other as the AI agent), then generate a connection token in the server's Settings tab. Send it to https://mcp.zapier.com/api/v1/connect in the Authorization header as a bearer token. Zapier also accepts the token as a token query parameter on the URL, but prefers the header because URLs end up in logs and config files. The token is shown once, is tied to that one server, and lets whoever holds it run the server's tools, so keep it in an environment variable or secret store. Rotating it immediately cuts off every client that uses it.

   docs.zapier.com/mcpdocs.zapier.com/mcp
5. List the server's tools

   Your client should list the server's tools. That confirms the connection, not every API permission.

   docs.zapier.com/mcp

What we observed

• 5 Nov 2026: HTTP 401 with WWW-Authenticate resource_metadata https://mcp.zapier.com/.well-known/oauth-protected-resource/api/v1/connect. The error body reads "Missing authorization header or token query parameter".