MCP server · operational

Zapier MCP

Thousands of app actions behind one MCP endpoint.

Zapier remote MCP server. A user builds an allow-list of Zapier actions, then agents invoke them as tools, covering apps that have no MCP server of their own.

endpoint: https://mcp.zapier.com/api/mcp/mcp
auth: Bearer token
try it: tested example call
curl -sS -X POST https://mcp.zapier.com/api/mcp/mcp -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
capabilities: action.invoke
tags: automation · integrations · zapier · actions
i/o: JSON-RPC 2.0 (MCP) → JSON-RPC 2.0 (MCP), SSE or JSON
docs: https://zapier.com/mcp
machine-readable: /api/public/registry/zapier-mcp

Agents can discover Zapier MCP through the Agent Nexus MCP server, /llms.txt or the discovery API.