The official Zapier MCP listing connects an MCP client to configured app actions. It is not limited to firing existing Zaps. Available actions depend on the connection's configuration, mode, and connected accounts.
Docs-derived; sources checked October 17, 2026. MCPFind did not connect a Zapier account, read a spreadsheet, or execute an action. Setup and tool behavior below follow how connections work, the Claude connection guide, and how tools work.
Connect with the current transport
Zapier documents this Streamable HTTP endpoint:
https://mcp.zapier.com/api/v1/connectUse your client's remote MCP connection interface and Zapier's client-specific instructions. OAuth is the preferred route in supported clients; a connection-token fallback is available where required. Keep tokens out of prompts and shared configuration. An old SSE configuration or an invented per-account URL is not a substitute for the current connection instructions.
After authorization, confirm the Zapier account and the app accounts attached to the connection. Review its enabled actions and operating mode. Zapier supports dynamic discovery, so ask the client to discover the relevant configured action and inspect its input schema before invoking it. Do not assume a tool is present merely because the app is connected, or that all app actions appear as a static tool list. See Zapier's tool and mode documentation.
Verify one read with a sample spreadsheet
Prepare a non-sensitive sample spreadsheet with a known name, sheet, columns, and two or three recognizable rows. Connect the intended spreadsheet account and enable only the read action needed for the test.
- Ask the client to discover an enabled spreadsheet read action and show its inputs. Confirm that it reads the named sheet rather than creating or updating rows.
- Supply the sample spreadsheet and sheet identifiers. Request only the known columns and a small row range supported by that action's schema.
- Expect the requested column names and sample values, with enough spreadsheet, sheet, or source identifiers to confirm the target. Compare them with the original sheet; stop if the account or target differs.
- Inspect Zapier's History for the operation, its inputs, and its outcome. An empty result, a permission error, and a successful read of zero rows require different follow-up.
This establishes one read path. It does not test every configured app action or establish that a later workflow is correct. Review current usage and plan limits in your account before expanding the task.
Review writes before enabling them
Sending a message, adding a spreadsheet row, updating a CRM record, or taking another action needs a separate review. Confirm the connected account, destination, proposed fields or message, and intended effect before granting that action. An action's availability is not approval to execute it.
Choose between Zapier and another automation integration by the exact app action, authentication, hosting, and review controls you need. For a different workflow architecture, see the n8n connection guide; compare it against your requirements rather than assuming either route is always preferable.
Adam Bush