Zapier MCP: one URL to more than 9,000 apps

Getting an agent to post in Slack, add a row to Google Sheets and create a lead in HubSpot normally means three MCP servers and three sets of credentials. Zapier MCP takes a different route. Zapier already connects to more than 9,000 apps, so it hosts one MCP server; you choose in Zapier which actions the agent may use, and the client connects to a single URL.

What it does

• Cross-app actions: send, search and create actions in Gmail, Slack, Google Sheets, Notion, HubSpot, Salesforce, Linear, Asana and thousands more, exposed as tools.
• Central authorization: app sign-ins happen in Zapier, the AI client never sees those credentials, and you limit which actions are exposed on the Zapier side.
• Client plugins: this repo distributes the in-client plugin, which adds guided onboarding, a demo and role-specific skills on top of the base connection for Claude Code, Cursor, Codex, Gemini CLI and others.
• Compliance: the project says the service is SOC 2 Type II certified, which helps with vendor reviews.

Who it’s for

• Ops, sales and marketing people who want an agent to handle repetitive work across SaaS tools without deploying servers one by one.
• Teams already automating with Zapier who want to hand those connections to an agent.

Setup

Needs a Zapier account. Clients like VS Code add the hosted URL directly (type http): https://mcp.zapier.com/api/v1/connect. In Gemini CLI, install the extension:

gemini extensions install https://github.com/zapier/zapier-mcp

Then run /mcp auth zapier. Claude Code users can install from the zapier/marketplace plugin marketplace; Zapier’s docs cover other clients.

Our take

The GitHub star count is modest (about 430 as of 2026-10-06) because the server itself runs in Zapier’s cloud and this repo only holds the client plugin. It makes the list for reach: the other gateways here help you manage servers you install, while Zapier hands over ready-made app connections, the lowest barrier for people who don’t write code. The trade-offs are just as clear. It’s a closed, commercial hosted service, your data passes through Zapier, and usage is bound by your Zapier plan; check Zapier’s pricing for the limits. The agent typically gets write access to send messages and change records, so expose as few actions as you can. The plugin repo is MIT-licensed.