What is a Zapier MCP server?
A Zapier MCP server exposes Zapier to AI agents as Model Context Protocol tools. Instead of a custom integration per agent, any MCP client can connect to the server and call the get_configuration_url tool to work with Zapier. The server in this catalog is the official Zapier MCP server, which authenticates with an API key.
What can you do with Zapier MCP?
Agents can set up a Zapier connection that links to thousands of apps and actions. The catalog lists one tool for this server, get_configuration_url, and its description is on this page.
Why put Zapier MCP behind an MCP gateway?
Connecting the Zapier MCP server directly to each client means a separate credential per developer, no inventory of who can reach Zapier through an agent, and no record of what agents did with it. An MCP gateway sits between every agent and the Zapier server, so sign-in runs through your identity provider, role-based access decides which teams can call which Zapier tools, and every call is inspected and logged in one place. The Speakeasy MCP Gateway applies those controls to Zapier and to every other server in your catalog.
How do you connect Zapier MCP through a gateway?
Add the Zapier server from the Speakeasy MCP catalog and every agent reaches it through one gateway URL, next to the rest of your approved servers. Authentication uses OAuth 2.1 with PKCE and dynamic client registration, sign-in runs through your identity provider, and role-based access controls decide which teams can use which Zapier tools. Every prompt, response, and tool call is inspected and logged at the gateway.
How is this different from an unofficial Zapier MCP?
Community-built Zapier MCP servers wrap the same Zapier surface but are not vendor-maintained. This catalog lists the official Zapier MCP server. Running it behind the Speakeasy MCP Gateway adds SSO, role-based access controls, and an audit trail of every call, whichever credential the server itself uses.
