Pipedream MCP
OfficialOne hosted MCP server for 2,800+ apps and 10,000+ tools, with Pipedream Connect managing OAuth for your users.
Add to your client
Copy the config for your MCP client and paste it into its config file.
npx @pipedream/mcpPaste into ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"pipedream-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://remote.mcp.pipedream.net/v3",
"--header",
"Authorization: Bearer <your-pipedream-access-token>",
"--header",
"x-pd-project-id: <your-project-id>",
"--header",
"x-pd-environment: development",
"--header",
"x-pd-external-user-id: <your-users-id>",
"--header",
"x-pd-app-slug: <app-slug-e.g.-slack>"
]
}
}
}Claude Desktop connects to remote servers through the `mcp-remote` proxy (installed on first run via npx). Restart Claude Desktop after saving.
Step-by-step guides: Add to Claude Desktop · Add to Cursor · Add to Windsurf
Before you start
- A Pipedream account and project (connected user accounts are stored in the project)
- A Pipedream OAuth client — exchange client credentials for the access token sent as the Bearer token
- For self-hosting the reference server: Node.js/pnpm and PIPEDREAM_CLIENT_ID, PIPEDREAM_CLIENT_SECRET, PIPEDREAM_PROJECT_ID, PIPEDREAM_PROJECT_ENVIRONMENT env vars
About Pipedream MCP
Pipedream MCP sits on top of Pipedream Connect, the managed-auth product: when one of your users connects Slack or Gmail, the OAuth grant lives in your Pipedream project, and MCP requests scoped to that user (x-pd-external-user-id header or externalUserId query param) execute with their stored credentials. The app scoping (header or ?app=slack) selects which app's tool set the server exposes; tools themselves are generated from Pipedream's registry of thousands of prebuilt actions.
Developer authentication is OAuth client credentials: create a Pipedream OAuth client, exchange it for a short-lived access token, and send it as a Bearer token alongside x-pd-project-id and x-pd-environment headers on every request to https://remote.mcp.pipedream.net/v3. Additional headers (x-pd-oauth-app-id, x-pd-account-id) cover custom OAuth apps and multi-account users. For personal, non-embedded use, mcp.pipedream.com wraps the same servers behind a browser UI where you connect accounts and copy per-app endpoints.
The self-hosted reference (npx @pipedream/mcp, or the modelcontextprotocol/ source with pnpm dev:http) shows the routing model — /{external_user_id}/{app} for SSE, /v1/{external_user_id}/{app} for streamable HTTP — but still calls the Connect API for auth and execution, so it isn't an offline or Pipedream-free option. Pipedream flags it as no longer actively maintained.
The trade-off is concentration: one vendor holds your users' third-party credentials and mediates every tool call, under a source-available (not OSI open-source) license for the platform code. In exchange you skip building OAuth for dozens of APIs, get dynamic app discovery for agent products, and inherit an integration catalog that would take years to replicate.
When to use it
- Give a support agent Slack, Gmail, and HubSpot tools where each end user connects their own accounts
- Embed MCP in your SaaS so customers' agents act on their behalf without you building per-API OAuth
- Prototype personal automations by connecting apps at mcp.pipedream.com and pasting the endpoint into your client
- Power a chat product with dynamic app discovery across 2,800+ APIs, the chat.pipedream.com pattern
Quick setup
- 1Sign up at pipedream.com and create a project — connected accounts will be stored there
- 2Create a Pipedream OAuth client and exchange the client credentials for an access token
- 3Point your MCP client at https://remote.mcp.pipedream.net/v3 with headers: Authorization: Bearer <token>, x-pd-project-id, x-pd-environment, x-pd-external-user-id, x-pd-app-slug
- 4Alternatively self-host the reference implementation: set the PIPEDREAM_* env vars and run npx @pipedream/mcp
- 5For quick personal use, connect apps in the browser at mcp.pipedream.com and use the per-app endpoints it gives you
Security notes
Your users' third-party OAuth grants and API keys are stored by Pipedream Connect, so you're delegating credential custody to Pipedream (their security docs detail how grants are handled); the Bearer access token and x-pd-project-id/x-pd-environment headers are secrets in their own right. The in-repo server is an unmaintained reference implementation — use the hosted remote server for production.
Pipedream MCP FAQ
Is Pipedream MCP free, and is it safe to hand over credentials?
Developing in a project's development environment is free; production Connect usage is billed per Pipedream's pricing. On safety: the entire value proposition is that Pipedream Connect stores and brokers your users' OAuth grants and keys per its published security docs — that custody trade-off (convenience vs. a third party holding credentials) is the main decision to make.
What's the difference between mcp.pipedream.com and remote.mcp.pipedream.net?
mcp.pipedream.com is the consumer-facing site: log in, connect your own accounts, copy per-app server endpoints. remote.mcp.pipedream.net/v3 is the developer endpoint for embedding MCP in your product, driven by Bearer auth plus headers/params that identify your project, your end user (externalUserId), and the target app.
Can I self-host it?
There's a reference implementation in the monorepo's modelcontextprotocol/ directory (npx @pipedream/mcp, SSE and streamable-HTTP routes per user and app), but Pipedream marks it unmaintained and it still depends on the hosted Connect API for auth and execution. It demonstrates the architecture; it is not a standalone alternative.
Alternatives to Pipedream MCP
Compare all alternatives →
Microsoft's official browser-automation MCP using Playwright's accessibility tree (no vision model).
Up-to-date, version-specific library documentation injected into your coding agent.
Pack any local or remote repository into one AI-ready file your agent can grep and read incrementally.
Compare Pipedream MCP with: