Pipedream Connect for AI agents: pricing, MCP and alternatives

What is Pipedream Connect?

Pipedream started as a workflow automation tool. Workday bought it in a deal announced in November 2025, and Pipedream now focuses on Connect: managed sign-in for 3,000+ APIs, 10,000+ prebuilt actions and triggers, an API proxy for calls no action covers, and a remote MCP server that serves those actions to any MCP client.

Pipedream's Workflows product is in maintenance mode and shuts down on March 31, 2027. Pipedream says Connect, its MCP servers and the API proxy are not affected. The code for Pipedream's integrations is public on GitHub under its own source-available license, which bars competing commercial use, so it is not open source, and the service can't be self-hosted. Pipedream says every plan is covered by SOC 2 Type 2 and GDPR, with HIPAA on its Business plan.

What is Pipedream MCP?

Pipedream MCP is Pipedream's remote MCP server. Any MCP client, such as Claude, Cursor or an agent you build, can connect to it and get the actions for an app as tools. Pipedream identifies each end user with an external user ID, runs the sign-in for that user, and calls the app's API as them. It is included in every Connect plan, and each tool call is billed like any other action.

Rakazo uses Pipedream through that server. It opens one MCP connection per connected account, so a person with two Gmail accounts gets two labeled sets of Gmail tools, and a bot can't mix them up.

Pipedream Connect pricing

Connect is billed on two meters: external users, the people your app connects accounts for, and credits. A credit buys 30 seconds of compute at the default 256 MB of memory, and running an action, an MCP tool call, a proxy request or a trigger event each uses at least one. Listing apps and accounts and other management calls are free. Most app actions finish well inside 30 seconds, so in practice one call is one credit; a slow call costs more.

Prices from Pipedream's pricing page and Connect environments docs, checked November 2026. A user counts once however many apps they connect.

• The development environment is for your own testing. It allows 10 external users, and connecting an app only works in a browser signed in to pipedream.com, so it can't serve a team.
• Credits scale with memory: an action given 1 GB uses four credits per 30 seconds.
• Unlike Composio, there is no free production tier. The smallest real deployment is $99 a month on a yearly plan.

What Rakazo bots cost on Pipedream

Rakazo gives Pipedream one external user per person per space, so someone in two spaces counts as two users. The examples assume one space and calls that finish within 30 seconds. A small team is 5 people whose bots run about 40 app actions each per workday, about 4,400 calls a month. A larger team is 20 people at about 100 actions each, about 44,000 calls.

Worked from Pipedream's pricing page, checked November 2026. Model usage and the bots' computers are billed separately, by your model provider or by Rakazo.

Pipedream vs Composio

They do the same job in Rakazo: a hosted catalog with managed sign-in. The difference is mostly price shape and catalog size. Composio is free for real use at small volume and cheap per call; Pipedream has about twice as many apps, a fixed monthly floor, and a per-user charge that grows with your team.

Prices from Pipedream and Composio, checked November 2026.

Pipedream alternatives

• Composio is the closest, built into Rakazo, and much cheaper for a small team.
• Zapier MCP reaches 9,000+ apps and spends 2 Zapier tasks per call; the free plan's 100 tasks cover about 50 calls and paid plans start at $19.99 a month billed yearly (pricing). It isn't built into Rakazo, but you can add it as a remote MCP server. It acts as the Zapier account that set it up.
• Arcade charges $25 a month plus $0.01 a call and focuses on authorization for each user. Nango publishes its source and suits teams adding integrations to their own product. Neither is built into Rakazo.
• For Pipedream Workflows users: Connect is not an automation builder. If you need scheduled workflows rather than tools for agents, look at n8n, Make or Windmill, or give a Rakazo bot a routine.
• No middleman: an app's own MCP server or an API connector adds no fee on top of the app.

What your bots can do with Pipedream

With Pipedream set up, the Apps list under Integrations shows every Pipedream app that has actions. Many are also in the catalog on the integrations page, such as HubSpot, Slack, Zendesk, Google Sheets and Jira.

• Connect an app on Pipedream's page. Choose Connect under Integrations, or ask a bot to connect it and use the card it posts. Pipedream's Connect Link opens for that app and you sign in there.
• Share it across the space. Once an app is connected, every bot in that space can use it.
• Use more than one account of the same app. Each connected account gets its own set of tools, labeled with the account. If that account goes away, Rakazo stops instead of using another one.
• Keep the tool list short. When the connected apps add up to more than 20 tools, bots get a searchable list instead of every tool up front.
• Ask before changes. Pipedream tools follow your approval settings like any other tool.
• Keep identities private. Pipedream sees an opaque ID for each person and space, not their name or email.

When to choose Pipedream

Choose Pipedream when you self-host Rakazo and already use Pipedream Connect, need an app only Pipedream covers, or want SOC 2 coverage without an enterprise contract. Its tools reach Rakazo through Pipedream's own MCP server, one connection per account.

Composio is the other managed option and the simpler one to set up: a single API key. You can run both, and the Apps list shows apps from each. On Rakazo Cloud you don't need a Pipedream account: connecting apps is part of every plan. For an app that publishes its own MCP server, or one you can reach with an API connector, you don't need a hosted middleman at all. The comparison puts them side by side.

Limits

• Pipedream's development environment is for testing with your own accounts. It allows 10 users, and connecting an app only works in a browser signed in to pipedream.com. Rakazo uses development unless you set production, which needs a Connect plan from Pipedream.
• Rakazo derives each person's Pipedream ID from ENCRYPTION_KEY. Change that key and existing Pipedream connections are orphaned and must be connected again.
• Logins live with Pipedream, not on your server, and every tool call goes through Pipedream's service.
• Pipedream is configured for the whole server. A space or user can't bring their own project.
• Rakazo refreshes Pipedream's app list every 10 minutes.

How to set it up

These steps are for the admin of a self-hosted Rakazo. Rakazo Cloud users don't need a Pipedream account; they connect apps from Integrations.

1. In Pipedream, create a project and an OAuth client for its API. Copy the client ID, client secret and project ID.
2. Set PIPEDREAM_CLIENT_ID, PIPEDREAM_CLIENT_SECRET and PIPEDREAM_PROJECT_ID on the Rakazo API and worker.
3. Set PIPEDREAM_ENVIRONMENT to development to test, or production for real users, then restart the API and worker.
4. Open Integrations in Rakazo, connect one app, and ask a bot to read something from it.