Back to Gap Map Product / UX / Agent tools & connectors

Zapier MCP

closed / Overall score: 4.4(strong)

Hosted MCP endpoint that puts Zapier's 9,000-app integration estate behind one connection: the client signs in through Zapier, Zapier holds the app credentials, and tool calls run as Zapier tasks.

Openness

1 high confidence

1.0

license: Proprietary(API-only)
source: closed(no self-hostable component
managed: cloud SaaS with API keys, two tasks per successful tool call against the account's Zapier plan

Closed and hosted end to end: one endpoint, no self-hosting option anywhere in the documentation, and the value is precisely the credential estate Zapier holds on the caller's behalf.

https://docs.zapier.com/mcp/overview/how-connections-work.md recorded 2026-09-17
The connections documentation: "Every MCP client connects to the same endpoint: https://mcp.zapier.com/api/v1/connect" and "Zapier MCP supports the Model Context Protocol over Streamable HTTP only." No self-hosted or source-available option appears.

Adoption

4 medium confidence

4.0

Adoption is read from platform activity Zapier publishes on its site - MCP servers created, tool calls completed, and apps connected - rather than any count of users, since no account or customer figure is broken out. Those are activity counts on the hosted product, not a measurement of how many people use it, so the reach is recorded in words rather than as a number.

https://zapier.com/mcp recorded 2026-09-17
The product page: "Connect AI tools to 9,000 apps with Zapier MCP", with a figures block reading "450,000+ MCP servers created", "18.5M+ tool calls completed" and "1M+ apps connected".

Capability

5 high confidence

5.0

Zapier covers many systems, holds every downstream app's credentials itself, and hosts execution end to end. Its own documentation states the point as plainly as any product in this category does: "Zapier holds the app credentials, so your MCP client never handles a third-party API key." Composio, scored on the same basis, sits at the same level.

https://docs.zapier.com/mcp/overview/how-connections-work.md recorded 2026-09-17
The connections page: "Zapier holds the app credentials, so your MCP client never handles a third-party API key." On the OAuth path: "The MCP client registers Zapier as an MCP server and sends you through a Zapier sign-in... You do not manage a credential: the MCP client stores and refreshes the OAuth token."
https://docs.zapier.com/mcp/quickstart.md recorded 2026-09-17
The quickstart: "If they have not connected that app in Zapier yet, execution prompts them to authenticate it."

Verified 2026-09-17