Cross-app actions
Expose actions for popular apps such as Gmail, Sheets, Calendar, Slack, Jira, Asana, and GitHub.
Documentation ↗MCP server / integration platform / source-linked
Zapier MCP
Zapier MCP provides one hosted endpoint for app actions already connected to a Zapier account. Current documentation specifies Streamable HTTP only, with OAuth for supported clients or a long-lived connection token for custom clients. The server holds third-party app credentials, while successful tool calls consume Zapier plan tasks.
Before you choose.
Identify the implementation and the job it supports.
Zapier MCP provides one hosted endpoint for app actions already connected to a Zapier account. Current documentation specifies Streamable HTTP only, with OAuth for supported clients or a long-lived connection token for custom clients. The server holds third-party app credentials, while successful tool calls consume Zapier plan tasks.
Setup and connection.
The documented interface, authentication and installation path.
- Connection / transport
- Streamable HTTP only
- Authentication
- OAuth for supported clients; connection token in Authorization header for other clients or custom code.
Connect https://mcp.zapier.com/api/v1/connect through the client quickstart, sign in, choose actions, and keep one server per named client. For custom clients create a server and token at mcp.zapier.com.
Setup reference ↗Documented setup example. Review the source and credentials before running; this command was not executed for this article.
https://mcp.zapier.com/api/v1/connectWhat it actually exposes.
Concrete capabilities with maintainer sources.
Credential brokering
Zapier keeps connected app credentials so the MCP client does not handle each third-party key.
Documentation ↗Client-specific servers
Provision one server per named MCP client and manage its selected actions/tool bundle.
Documentation ↗Evidence and method.
What was checked and what was not tested.
HOW
Source method
Public maintainer documentation and repositories. This is not a hands-on product review.
WHEN
Last checked 2026-10-01
Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.
Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.
Community signals.
Concrete reports from public community discussions, kept separate from product documentation.
Signal: onboarding and client compatibility
Zapier opened the thread specifically to collect post-setup connection feedback, showing that client compatibility and the handoff after server creation are active user questions.
“what happens after you set up your server and go to connect in your AI client”Open community source ↗
Signal: per user oauth friction
A complaint about integrating Zapier MCP says each end user must manually complete a setup or connection step, highlighting the operational cost of per-user authorization.
“Every user has to do this manually.”Open community source ↗
Signal: troubleshooting observability
A commenter says failed connections leave users guessing, so setup documentation should include actionable error states and a reconnect path.
“lack of clear troubleshooting feedback when connections fail”Open community source ↗
Community evidence is anecdotal and may reflect one setup, version or account. It is included for discovery and risk-sensing, not as a representative rating or independent benchmark. Verify the current official documentation before acting on a report.
Try a specific task.
A bounded evaluation you can reproduce in your own environment.
Cross-app handoff
Suggested evaluation, not an observed test result.
- Connect one client through OAuth and select only the app actions needed.
- Ask the agent to draft a cross-app update and show target records before execution.
- Approve the call, then inspect the task usage and resulting records.
What to inspect: A visible, auditable action chain across connected apps with predictable task accounting. Record the client, selected scope, date, and approval checkpoint so readers can reproduce the decision. Proposed workflow; not tested by clawbot.ai.
Workflow reference ↗Permissions and limitations.
Read these constraints before granting access.
SSE-only MCP clients cannot connect because Zapier supports Streamable HTTP only.
Boundary reference ↗Each successful call uses two Zapier tasks; sharing servers requires Team or Enterprise, according to the limitations page.
Boundary reference ↗Decide by workflow.
Make the expected output explicit before you connect.
A visible, auditable action chain across connected apps with predictable task accounting. Record the client, selected scope, date, and approval checkpoint so readers can reproduce the decision. Proposed workflow; not tested by clawbot.ai.
Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.
Compare the alternatives.
Specific reasons to choose another route, with the tradeoff shown.
| Alternative | Choose it when | Tradeoff |
|---|---|---|
| Composio MCP | Choose for dynamic per-user sessions and fine-grained toolkit/tool policies. | Composio is more configurable; Zapier is simpler for existing Zapier app connections. Documentation ↗ |
| Pipedream MCP | Choose when you need custom tools and app discovery in your own product. | Pipedream requires more developer-side identity headers and OAuth plumbing. Documentation ↗ |
Questions before setup.
Answers specific to this implementation.
Can a client use SSE?
No. Zapier MCP supports Streamable HTTP only.
Documentation ↗
Does the client see app API keys?
No. Zapier holds the app credentials; OAuth or a connection token authenticates the MCP server.
Documentation ↗
Source trail.
Maintainer documentation used in this record.