Pipedream MCP server
Pipedream's official MCP server: connect an agent to 2,800+ apps and 10,000+ prebuilt actions, with managed OAuth and per-app endpoints.
Pipedream MCP is Pipedream's official server, built on Pipedream Connect, that gives an AI agent access to a registry of 2,800+ integrated apps and over 10,000 prebuilt actions and triggers. Instead of standing up a separate MCP server for every SaaS app, you point the agent at Pipedream and it can connect accounts, configure parameters, and make API requests — send a Slack message, create a GitHub issue, query a database, add a Notion page — all as tool calls. Pipedream manages the OAuth and credential storage: user credentials are encrypted at rest and every request flows through Pipedream's servers, so tokens are never exposed to the model.
The canonical deployment is the hosted remote server at https://mcp.pipedream.com, which uses per-app routing — each app gets its own endpoint (for example https://mcp.pipedream.com/app/slack), so the tools available at that endpoint are exactly the actions for that app, keeping the context window focused. Authentication is OAuth, and accounts are connected through Pipedream. For developers building this into their own product, the reference server can be self-hosted via npx @pipedream/mcp using a Connect project's client ID, client secret, project ID, and environment, with routes scoped per end user. Because the tool surface for each endpoint is generated dynamically from Pipedream's action registry, there is no single fixed built-in tool list.
Quick install
Copy-paste configs are provided for all 8 supported clients. Pick your client below.
Add to ~/.claude.json
{
"mcpServers": {
"pipedream": {
"type": "http",
"url": "https://mcp.pipedream.com"
}
}
}claude mcp add --transport http pipedream https://mcp.pipedream.comHeads up
- First tool call opens a browser to authorize.
Required configuration
- PIPEDREAM_CLIENT_IDOptional
Client ID of your Pipedream Connect OAuth app. Self-hosting only.
- PIPEDREAM_CLIENT_SECRETOptional
Client secret of your Pipedream Connect OAuth app. Self-hosting only.
- PIPEDREAM_PROJECT_IDOptional
ID of your Pipedream Connect project. Self-hosting only.
- PIPEDREAM_PROJECT_ENVIRONMENTOptional
Connect environment, 'development' or 'production'. Self-hosting only.
What you can do with it
Reach thousands of apps without per-app setup
The agent connects to a Pipedream app endpoint such as /app/github or /app/slack and immediately has that app's prebuilt actions as tools. Pipedream runs the OAuth and stores credentials encrypted, so the agent never sees raw tokens.
Embed managed tool calling in your product
A developer self-hosts the reference server via npx @pipedream/mcp with their Connect project credentials, scoping routes per end user, so their own application's agent can act on each user's connected accounts with managed auth.
FAQ
- Is it free?
- Pipedream has a free tier that covers individual use across connected apps, with paid plans for higher usage, more connected accounts, and team features. The MCP server itself is part of Pipedream Connect; usage of each underlying app follows your own accounts and credentials.
- Does it support remote/OAuth?
- Yes. The canonical deployment is the remote server at https://mcp.pipedream.com with OAuth and per-app routing (e.g. /app/slack). Pipedream manages and encrypts credentials so tokens are never exposed to the model. Developers can also self-host the reference server via npx @pipedream/mcp using Connect project credentials.