Specific implementation researched
Zapier MCP
Implementation, permissions and documented client compatibility.
A directory listing or verification does not replace a security audit. No installation is triggered automatically here. Do not enter API keys in public forms.
What is specifically documented?
- Connected service
- Zapier
- Publisher
- Zapier
- Origin
- Officially from the named publisher
- Deployment mode
- Remote
- Transport
- Streamable HTTP; SSE wird nicht unterstützt.
- Authentication
- OAuth for many clients; a connection token for custom integrations.
- Read capabilities
- Query data through authorized app actions
- Write capabilities
- Send messages, create tasks and change records through authorized actions
- Permissions
- Workspace permissions, app connections and enabled actions determine access. Agentic Mode can add actions dynamically; Managed Mode uses a fixed selection.
- Required plan
- No confirmed information
- Additional costs
- According to the quickstart, a successful tool call consumes two tasks from the Zapier plan; failed calls do not count.
- Maintenance status
- No confirmed information
- Review date
- 11/10/2026
Support by client
Documented setup is not an independent functional test. General MCP support does not imply full compatibility.
| Client | Status | Source |
|---|---|---|
| Claude Desktop | Setup documented | Documentation ↗ |
| Claude Code | Setup documented | Documentation ↗ |
| Claude Web | Setup documented | Documentation ↗ |
| Cursor | Setup documented | Documentation ↗ |
Sources & implementation
How Zapier MCP connections work: OAuth and connection tokens ↗Retrieved on 11/10/2026. Provider statements, not a security audit.
Implementation: https://mcp.zapier.com/api/v1/connect