Can AI agents automate Zapier?

Zapier is automatable today through first-party Zapier MCP. Clients connect over Streamable HTTP to https://mcp.zapier.com/api/v1/connect with OAuth inside supported clients or a connection token created at mcp.zapier.com. The server exposes 9,000-plus app integrations and 40,000-plus actions under workspace access controls. Zapier is SOC 2 Type II certified. Each successful tool call consumes two tasks from the same Zapier plan used by Zaps; failed calls do not count. Sharing a server needs a Team or Enterprise plan. SSE clients cannot connect. Next Gen Zap workflows through MCP are early access. Zapier MCP is an interface to Zapier, not a substitute for each connected app's own record. The Workflow REST API at api.zapier.com can list and create Zaps with OAuth 2.0 user access tokens, but client credentials are available only after publishing a public App Directory integration, so that path is partner-gated. Official TypeScript SDK (@zapier/zapier-sdk) and zapier-sdk CLI are in open beta and free during early access; Enterprise workspaces are off by default. This record excludes n8n, Microsoft Power Automate, and Make. Computer-use viability is unassessed. MCP scores 8 and is the best path.

Best path today: mcp · Overall automatability: 8/10