Skip to directory

About Zapier MCP

Zapier MCP exposes selected single actions from the apps connected to a user’s Zapier account; tools can be discovered and enabled as needed or configured as a fixed tool list.

What you can use it for

  • Cross-app automation actions
Connection and setup
Hosting
Vendor-hosted remote MCP
Transport
Streamable HTTP
Endpoint
https://mcp.zapier.com
Authentication
Sign in to Zapier and authorize the connected app accounts.

Requirements

  • Zapier account
  • At least one app connected to the Zapier account
  • MCP-compatible AI client
  • Action availability and usage may depend on Zapier plan and account limits

Setup steps

  1. Open `https://mcp.zapier.com` and create a new MCP server, choosing the target AI client or Other.
  2. Add only the app actions the agent should be able to perform. Authenticate each app account when requested and provide required action fields.
  3. Save the selected tools; copy the client-specific integration URL/configuration Zapier generates. Do not copy the URL into public logs if it contains access material.
  4. Add the generated endpoint to the selected MCP client following Zapier's client-specific Connect instructions.
  5. Test by asking the assistant to list available tools. Before write actions, review which configured actions can send messages, create records, or otherwise change external apps.
Tools 1+

Tools are discovered dynamically from connected apps unless a fixed set is configured.

  • dynamic_tool_discovery

    Search Zapier’s action catalog and add, configure, and manage tools dynamically at runtime.

    01

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

Limitations and notes
  • Action names are user-selected and server-specific, covering thousands of apps and tens of thousands of actions; there is no universal static identifier inventory. Each successful MCP tool call uses two Zapier tasks.
Original sources
  • Source

    Recorded fields: overview, endpoint and clients.

  • Source

    Recorded fields: server setup interface.

  • official publisher documentation

    Tool roster is generated from each configured server, so no universal exact names are stored.

  • official documentation

    Current publisher or maintainer documentation reviewed 2026-10-28T19:00:00.000Z.

  • third party tool list capture

    APIs.io MCP server page records dynamic_tool_discovery as the server meta-tool for searching the action catalog and adding/configuring/managing actions at runtime. This is a published capture, not a live authenticated tools/list response.

Documentation checked 2026-10-28T19:00:00.000Z. Connection has not been runtime tested.