Pipedream Connect MCP
Pipedream Connect's MCP exposes its huge app-action catalog (Slack, Notion, Airtable, 2,700+ apps) through one remote endpoint backed by your connected accounts.
- Provider
- Pipedream โ
- Source
- https://github.com/PipedreamHQ/pipedream โ
- Categories
- ๐ Multi-App Gateways & Automation
ไธญๆ็ฎไป
Pipedream ่ฟ็จ MCP ็ฝๅ ณใ้่ฟไธไธช OAuth ไฟๆค็็ซฏ็น่ฟ่ก 2700+ ๅบ็จๅจไฝไธๆ็ฎก่งฆๅๅจใ
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"pipedream": {
"url": "https://remote.mcp.pipedream.net"
}
}
}claude mcp add --transport http pipedream https://remote.mcp.pipedream.net
Or add to .vscode/mcp.json:
{
"servers": {
"pipedream": {
"type": "http",
"url": "https://remote.mcp.pipedream.net"
}
}
}- Open Settings โ Connectors (Integrations) โ Add Custom Connector.
- Paste the endpoint URL:
https://remote.mcp.pipedream.net - Complete the browser OAuth 2.1 login flow when prompted.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"pipedream": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://remote.mcp.pipedream.net"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"pipedream": {
"serverUrl": "https://remote.mcp.pipedream.net"
}
}
}๐งฐ Tools exposed by Pipedream MCP (3)
| Tool | Safety | Description | Parameters |
|---|---|---|---|
| run_pipedream_action | ๐ Write | Run a Pipedream action against a connected app account. | action*: stringparams: object |
| list_available_triggers | ๐ข Read | List trigger sources available for a connected app. | app: string |
| proxy_api_request | ๐ Write | Proxy an API request to a connected app's account. | app*: stringmethod*: stringurl*: stringbody: object |
๐ OAuth 2.1 & Security
- Auth type
- OAuth 2.1
- Dynamic Client Registration
- โ Supported
- PKCE S256
- โ Supported
- Protected resource metadata
- https://remote.mcp.pipedream.net/.well-known/oauth-protected-resource (expected location)
๐งฉ Recommended Agent Skills
๐ Guide
Pipedream MCP โ Remote MCP Server
Pipedream Connect is designed for developers embedding integrations: the remote MCP fronts the same catalog that powers Pipedream workflows, so an agent can run app actions and proxy API calls against accounts your users connect. OAuth handles account linking; the endpoint speaks Streamable HTTP.
Endpoint & Transport
- Endpoint URL:
https://remote.mcp.pipedream.net - Transport: Streamable HTTP
Authentication
Pipedream MCP uses OAuth 2.1 โ the first request returns a 401 Unauthorized challenge with a WWW-Authenticate header pointing at the authorization metadata. Compliant clients (Cursor, Claude, VS Code, ChatGPT) handle the whole flow โ PKCE and Dynamic Client Registration, so no manual client setup is needed โ and simply open a browser consent screen.
Available Tools (3)
| Tool | Safety | Description |
|---|---|---|
run_pipedream_action |
write | Run a Pipedream action against a connected app account. |
list_available_triggers |
read | List trigger sources available for a connected app. |
proxy_api_request |
write | Proxy an API request to a connected app's account. |
Connect in 30 Seconds
Claude Code โ one command:
claude mcp add --transport http pipedream https://remote.mcp.pipedream.net
Cursor โ add to ~/.cursor/mcp.json:
{ "mcpServers": { "pipedream": { "url": "https://remote.mcp.pipedream.net" } } }
VS Code โ add to .vscode/mcp.json:
{ "servers": { "pipedream": { "type": "http", "url": "https://remote.mcp.pipedream.net" } } }
Claude Desktop & stdio clients โ bridge with mcp-remote:
{ "mcpServers": { "pipedream": { "command": "npx", "args": ["-y", "mcp-remote", "https://remote.mcp.pipedream.net"] } } }
On first connect your client opens a browser OAuth consent screen โ approve it and tools become available immediately.
Troubleshooting
- 401 Unauthorized on connect โ that's expected; the server is OAuth-protected. Let your client complete the browser consent flow, or inspect the endpoint in our OAuth debugger to see the exact
WWW-Authenticatechallenge. - "Session expired" / stale
Mcp-Session-Idโ just re-sendinitialize; stateless clients can ignore session headers entirely. - Your endpoint is scoped to a Pipedream project and external user id โ see your Connect dashboard.
- Useful when you need many apps but want managed auth and per-user account isolation.
๐ How to Connect
- Copy the Pipedream MCP endpoint URLThe remote endpoint is https://remote.mcp.pipedream.net.
- Add it to your MCP clientClaude Code:
claude mcp add --transport http pipedream https://remote.mcp.pipedream.net. Cursor: add"pipedream": { "url": "https://remote.mcp.pipedream.net" }undermcpServersin ~/.cursor/mcp.json. Other clients work similarly. - Complete the OAuth consentOn first connection your client opens a Pipedream consent screen in the browser. Approve it to grant access; the token is stored by the client and refreshed automatically.
- Verify with the online inspectorPaste https://remote.mcp.pipedream.net into remotemcp.net/inspector, run initialize and tools/list, and confirm Pipedream MCP's 3 tools respond.
โ FAQ
What is the Pipedream MCP remote MCP endpoint?
The primary endpoint is https://remote.mcp.pipedream.net. It is a hosted gateway server operated by Pipedream, speaking the Streamable HTTP transport.
How do I authenticate with Pipedream MCP?
Pipedream MCP uses OAuth 2.1. When your client first connects it receives a 401 challenge, discovers the authorization server via RFC 9728 metadata, and opens a browser consent screen. Dynamic Client Registration is supported, so compliant clients register themselves automatically.
I'm getting a 401 Unauthorized from Pipedream MCP โ what's wrong?
A 401 means your client hasn't completed (or has lost) the OAuth authorization. Remove and re-add the server in your client to restart the consent flow, and check that your browser session can reach the provider's login page. If the 401 arrives without a WWW-Authenticate header, run it through our OAuth debugger to see what's missing.
Which MCP clients work with Pipedream MCP?
Any client that supports remote MCP servers: Cursor, Claude Code (`claude mcp add --transport http pipedream https://remote.mcp.pipedream.net`), VS Code Copilot, ChatGPT connectors, Windsurf, and Claude Desktop via the `mcp-remote` bridge.
What tools does Pipedream MCP expose?
3 tools are cataloged in this directory โ including `run_pipedream_action`, `list_available_triggers`, `proxy_api_request`. Use our online inspector to fetch the live tool list straight from the endpoint.
๐ Connect Guides
๐ Embed Status Badge in README
Related Servers
Zapier's MCP gateway โ one endpoint that proxies thousands of app actions (Gmail, Slack, Sheets...) as MCP tools with your Zapier-connected accounts.
Composio's remote MCP gateway exposing 250+ SaaS toolkits (GitHub, Slack, Notion...) with managed OAuth โ one endpoint for multi-app agent workflows.