Pipedream MCP server
OFFICIAL SERVERSelf-hosted stdio or SSE MCP server that runs Pipedream's prebuilt actions for one connected app
Hosted MCP access to the actions of Pipedream's 3,000+ app integrations, with Pipedream handling sign-in
Official · Pipedream JavaScript Remote (hosted) · Streamable HTTP ProductivityCommunicationDeveloper tools
57 popularity score ★ 12k
Opens the app, which asks before it adds the server.
claude mcp add --transport http pipedream https://mcp.pipedream.net/v2https://mcp.pipedream.net/v2https://mcp.pipedream.net/v2{
"mcpServers": {
"pipedream": {
"url": "https://mcp.pipedream.net/v2"
}
}
}{
"servers": {
"pipedream": {
"type": "http",
"url": "https://mcp.pipedream.net/v2"
}
}
}[mcp_servers.pipedream]
url = "https://mcp.pipedream.net/v2"gemini mcp add --scope user --transport http pipedream https://mcp.pipedream.net/v2Pipedream MCP is a hosted endpoint run by Pipedream that turns the pre-built actions of its integration platform into MCP tools. Each supported app (Slack, GitHub, Google Sheets, Notion, Linear, Stripe, PostgreSQL and thousands more) has its own set of tools, and Pipedream's docs put the total above 10,000 tools across more than 3,000 APIs. An assistant can then do things such as post a Slack message, file a GitHub issue or add rows to a sheet using accounts the user has connected.
There are two ways in. End users add https://mcp.pipedream.net/v2 to a client such as Claude, ChatGPT, Cursor or VS Code, sign in to Pipedream through OAuth, and pick which apps to enable. Developers building their own agent connect to https://remote.mcp.pipedream.net/v3 with a client-credentials access token and headers naming their project, environment, end-user ID and app slug, so the server acts for each of their users. When a tool needs an account the user has not connected, the server answers with a Connect Link URL for the user to open rather than failing outright.
The GitHub repository is Pipedream's public components monorepo: the action code the tools are generated from lives in its components directory, but the repository README does not describe the MCP server, and there is no supported package to run it locally. Tool-call failures come back as MCP results with isError set and an attribution field saying whether the fault was in the tool code, the upstream API or the network.
A Pipedream MCP account (created on first sign-in at mcp.pipedream.net) and an MCP client that supports remote servers with OAuth; ChatGPT and Claude custom connectors are only on certain plans of those products. For the developer endpoint: a Pipedream account, a Connect project, and OAuth client credentials (PIPEDREAM_CLIENT_ID, PIPEDREAM_CLIENT_SECRET, PIPEDREAM_PROJECT_ID, PIPEDREAM_ENVIRONMENT) to mint the bearer token.
Runs only as Pipedream's hosted service; no local install is documented. Pipedream MCP accounts are separate from pipedream.com accounts. Tool names are prefixed with the name you give the server in your client, so a long server name can push them past a client's tool-name length limit (the MCP spec suggests 128 characters); the docs advise a short name such as "PD". The developer endpoint is free in development mode, and shipping to production for your users falls under Pipedream's paid pricing; personal use of the hosted servers is free.
Suits someone who wants one connection that reaches many SaaS apps without setting up a separate server and credentials for each, and is content to let Pipedream hold the OAuth tokens and route every call through its servers. Also suits developers building agents that act for many end users, since account connection and token storage are handled for them. Pick a dedicated self-hosted server for a single app instead when credentials must stay on your own machine or network, or when you need to read and audit exactly which code runs.