Zapier MCP

Zapier's value has always been that it already holds authenticated connections to nearly every SaaS product a company uses. Zapier MCP turns that estate into tools an agent can call, which is a materially different proposition from wiring up individual MCP servers one integration at a time: one connection, and Gmail, Slack, HubSpot, Google Sheets, Notion, Jira and thousands more become available without a separate OAuth dance for each.

The scoping model is the important detail. You do not hand an agent all 8,000 apps. At mcp.zapier.com you create a named MCP server and choose the specific actions it may take — "send a Slack message to #alerts", "append a row to this sheet", "create a HubSpot contact". Each server gets its own connection token. That means a research agent and a deployment agent can hold genuinely different permissions, and the blast radius of a misbehaving prompt is bounded by a list you wrote rather than by the model's judgement.

Connection: the hosted endpoint is https://mcp.zapier.com/api/v1/connect. The setup portal generates a client-specific configuration for ChatGPT, Claude, Cursor, VS Code, Windsurf, Microsoft Copilot Studio or a generic client.

Authentication: OAuth is the smoothest path — the first connection opens a browser to sign in and authorise, then the credentials are reused. Alternatively, generate a connection token and send it as Authorization: Bearer <token>, or pass it as a query parameter on the server URL. Copy the token when it is generated; it is not shown again.

Good for: agents that need to act in business systems rather than only read from them — filing tickets, updating a CRM, posting notifications, moving records between tools — where standing up and maintaining a separate MCP server per product is not worth the effort.

Worth knowing: actions run through Zapier and count against your Zapier plan's usage, so the pricing and rate characteristics are those of your Zapier account, not of a standalone server.