Quick answer: pick Zapier MCP if you want to give your own AI assistant access to thousands of apps with no code and you already pay for Zapier. Pick Composio MCP if you are building an AI product where each of your users connects their own accounts and you want a developer platform with per-user auth and low per-call pricing. Pick Pipedream MCP if you want per-app MCP servers backed by managed end-user OAuth and you are comfortable with credit-based billing from a company that is now part of Workday.
All three are hosted MCP server options that sit between an AI client and a large catalog of SaaS APIs. They handle credentials so the model never sees them. The differences show up in who the product is built for, how tools are exposed to the model, and how you pay. Here is how they compare as of October 2026.
| Feature | Zapier MCP | Composio | Pipedream MCP |
|---|---|---|---|
| What it is | Hosted MCP server on top of Zapier’s app catalog | Developer platform for agent tools, auth and an MCP gateway | Per-app hosted MCP servers powered by Pipedream Connect |
| Best for | Individuals and teams wiring AI clients to their apps | Developers building multi-user AI agents and products | Developers embedding integrations and MCP tools in apps |
| Ownership | Zapier (independent) | Composio (independent) | Workday (acquisition closed by early 2026) |
| App coverage | 9,000+ apps | 1,500+ toolkits | 3,000+ apps |
| Actions / tools | 30,000+ actions (Zapier cites up to 66,000+ triggers and actions) | Tools per toolkit, loaded on demand in sessions | 10,000+ tools |
| Auth handling | Zapier-managed connections, acting as the account owner | Managed or bring-your-own OAuth per user ID | Managed end-user OAuth and API keys via Connect |
| Multi-user production | Embed option available; core product is single-account | Core design goal | Core design goal (Connect) |
| Pricing model | Two Zapier tasks per tool call | Tool calls (free allowance, then per call) | Compute credits plus external users |
| Free tier | 100 tasks a month (about 50 tool calls) | 100,000 tool calls a month | Free for personal use and development mode |
| Entry paid plan | Professional from $19.99 a month | Pro at $29 a month | Startup at $99 a month billed annually |
| Compliance claims | SOC 2 Type II | SOC 2 Type II and ISO 27001 | SOC 2 Type 2 report on request, BAAs available |
The core difference is the intended user. Zapier MCP is an extension of Zapier for people who use AI clients like Claude, ChatGPT and Cursor. You pick which actions to expose, Zapier gives you a server URL, and the agent acts through your existing Zapier connections. It is the fastest route from “I want Claude to update my CRM” to it working.
Composio and Pipedream are developer infrastructure. Both are built around the idea that your product has many end users, each of whom connects their own Gmail, Slack or Salesforce, and your agent acts for each of them separately. Composio leans into agent-specific features such as sessions that load tools on demand and in-chat Connect Links. Pipedream exposes a dedicated MCP server per app and bundles MCP with its wider Connect toolkit for embedding integrations, proxying API calls and running workflows.
If you are still deciding whether you need a hosted multi-app server at all, our list of the best MCP servers covers single-app, vendor-run options.
Zapier has the largest catalog of the three, with more than 9,000 apps. Zapier’s own pages cite 30,000+ actions in some places and 66,000+ triggers and actions in others, so treat the exact figure loosely. The practical point is that if an app has a Zapier integration, your agent can probably reach it. When no prebuilt action fits, the agent can write and run custom code.
Composio lists more than 1,500 toolkits, covering the common business stack (Gmail, Slack, GitHub, Salesforce, Notion, HubSpot and many more). Its catalog is smaller than Zapier’s but built specifically for agents, with tools designed to be called by a model rather than adapted from automation steps. You can also add your own custom MCP servers.
Pipedream covers more than 3,000 apps and over 10,000 prebuilt tools, generated from its registry of open source actions. Each app gets its own MCP server (for example, one URL for Slack and another for GitHub), which keeps tool lists focused per app.
This matters more than catalog size, because every tool definition consumes context and too many tools degrade the model’s choices.
With Zapier MCP, you choose the specific actions to expose for each server in a no-code dashboard and can control how the AI fills each field. The agent can also search the catalog for the right action. Skills you save in one client can be reused across other supported clients.
Composio offers two modes. Single Toolkit MCP creates a server scoped to selected toolkits and an allowed-tools list, with a per-user URL. Composio now recommends sessions for most use cases: a small set of meta tools search the catalog, load only the tools a task needs, manage connections and execute calls, keeping the model’s context lean.
Pipedream takes the per-app route. You connect the app servers you need, and each exposes tools specific to that API. For broad, unpredictable tasks you may end up connecting several servers. For narrow agents it is clean and predictable.
Zapier keeps app credentials in its managed connection layer, so the agent only receives a server URL or connection token. By default, actions run as the Zapier account owner. That is ideal for personal and team use but not for a product where hundreds of customers each need their own connections. Zapier does offer an embed option that issues a unique MCP server URL per end user of your product, authenticated with your embed secret, which narrows the gap for developers already invested in Zapier.
Multi-user auth is Composio’s center of gravity. Every connection belongs to a user ID you choose, and every tool call runs with that user’s credentials. Composio’s managed OAuth works out of the box, or you can bring your own OAuth app and white-label the flow. When a user has not yet connected an account, the agent can hand them a hosted Connect Link in chat. Tokens refresh automatically, and a webhook warns you when a connection expires.
Pipedream Connect handles OAuth and API key collection for your end users through a client SDK or a hosted Connect Link, with Pipedream-approved OAuth clients or your own. Credentials are encrypted at rest and never exposed to the model or client-side code, and API requests route through Pipedream’s servers. Pipedream says it does not store request payloads or response bodies.
Zapier MCP needs no code for its main use case. Guided setup covers Claude, ChatGPT and Cursor, and other MCP clients connect with a token. For developers there are Python and TypeScript SDKs that call Zapier MCP with an API key; Zapier describes the SDK as free during its beta.
Composio is code-first. Its Python and TypeScript SDKs create sessions and MCP servers, generate per-user URLs, manage auth configs and execute tools, and the platform is model and framework agnostic. If you are building with LangGraph, CrewAI or the OpenAI and Anthropic SDKs, it slots in as the tool layer. See our AI agent frameworks list for context.
Pipedream offers a TypeScript SDK and REST API for Connect, a component registry, a proxy for custom API calls, and its visual workflow builder. The breadth is useful if you also need triggers and workflows, not just MCP tools.
Zapier MCP is included on every Zapier plan with no separate contract. Each MCP tool call uses two tasks from the same quota your Zaps draw on. The free plan’s 100 tasks a month works out to roughly 50 tool calls, and paid plans start at $19.99 a month (Professional) and $69 a month (Team), with task volume set by a slider. Heavy agent use can drain a shared task pool quickly, so budget for it. If cost is pushing you away, our guide on how to cancel Zapier covers the steps.
Composio’s current pricing page lists a free Hobby plan with 100,000 tool calls a month (usage pauses at the cap), a Pro plan at $29 a month that includes 100,000 calls plus a $29 usage credit and charges $0.0003 per extra call, and custom Enterprise pricing with SSO, SCIM and customer-managed keys. Composio has changed its pricing more than once in 2026, so confirm the live page before committing.
Hosted Pipedream MCP servers are free for personal use, and development mode with full API, SDK and MCP access is free. Serving real end users in production requires the Startup plan at 150 monthly), which includes 10,000 credits and 100 external users, then $2 per additional user per month and $0.012 per extra credit. A credit covers 30 seconds of compute. Business plans are custom.
Zapier states it is SOC 2 Type II certified and gives admins app-level and action-level controls, logs every MCP action in History, and lets Enterprise IT enable MCP per workspace. Composio states SOC 2 Type II and ISO 27001:2022 compliance, and Enterprise adds SSO, SCIM, customer-managed keys and BAAs. Pipedream says it can provide a SOC 2 Type 2 report on request and can sign BAAs for customers handling health data.
Ownership is the other factor. Workday announced its agreement to acquire Pipedream in November 2025, and Workday’s January 2026 results confirmed the deal had closed. Pipedream’s product and pricing pages are still live and the product is still sold, but buyers planning multi-year builds should ask about the roadmap under Workday. Zapier and Composio remain independent.
You want your own AI assistant to act across many apps today, without writing code, and your team already runs on Zapier. It has the widest catalog and the easiest setup. It is a weaker fit for a multi-tenant product or high call volumes, where the two-tasks-per-call model gets expensive.
You are building an AI agent or SaaS feature where each customer connects their own accounts, and you want per-user auth, on-demand tool loading and a generous free allowance. It is the most agent-focused of the three. For other options in this space, see our Composio alternatives list.
You want dedicated per-app MCP servers plus a broader integration toolkit (proxy, triggers, workflows) for embedding in your app, and credit-plus-user pricing fits your usage. Factor in the Workday ownership when planning long term.
If you only need deep access to two or three systems, vendor-run servers from GitHub, Notion, Atlassian or Stripe are often better than any aggregator. If you need custom integrations at scale, an enterprise AI agent development firm can build and govern them for you.
It is included on Zapier’s free plan, but tool calls consume two tasks each from the 100 monthly tasks, so you get roughly 50 calls before you need a paid plan.
Composio MCP is Composio’s way of exposing its 1,500+ toolkits to any MCP client, either as toolkit-scoped servers with per-user URLs or through sessions that load tools on demand, with Composio handling each user’s authentication.
For building a product with many end users, Composio is designed for that job and its per-call pricing is far lower at volume. For a developer automating their own work, Zapier MCP is quicker to set up and reaches more apps.
Yes. As of October 2026, Pipedream’s MCP servers, Connect and pricing plans are live and documented. The acquisition closed in early 2026.
Zapier MCP, Composio and Pipedream MCP all remove the pain of managing OAuth tokens for AI agents, but they serve different buyers. Zapier is the no-code choice for people and teams using AI clients. Composio is the developer platform for multi-user agents. Pipedream is a capable middle option with per-app servers and a wider integration toolkit, now under Workday.
Start with who will connect accounts, you or your customers, and how many tool calls you expect each month. Those two answers usually settle the choice. For a wider view of this category, see our comparison of Composio vs n8n vs Zapier.