Pipedream Source Available License v1.0 — not OSI-OSS. Read the LICENSE before redistributing.

The reference implementation is no longer actively maintained. Pipedream recommends the hosted remote MCP at mcp.pipedream.com for production.

How is OAuth managed?

Pipedream handles the OAuth flow + token storage for end-user app connections. You pass an external user ID; tokens are mapped automatically.

Pipedream

Name: Top MCPs — curated MCP directory
Creator: Top MCPs
License: https://creativecommons.org/licenses/by/4.0/

Official

2,800+ apps and managed OAuth via Pipedream's hosted MCP at mcp.pipedream.com.

Score 82(?)PipedreamOther 11kVerified May 27, 2026Top MCPs for Automation & Workflows →

Install View on GitHub

Quick answer

What it does

Surfaces Pipedream's catalog of 2,800+ app integrations as MCP tools, with managed OAuth, credential storage, and per-end-user identity mapping.

Best for

Multi-app agent products
Managed OAuth for end-users
Production multi-tenant apps
Action-taking across 2,800+ services

Not for

Truly OSS-only stacks (Source Available license)
One-off scripts (use Zapier MCP)

Setup recipe

Pick your client, then follow the three steps.

Install

claude_desktop_config.jsonjson

{
  "mcpServers": {
    "pipedream": {
      "command": "npx",
      "args": [
        "@pipedream/mcp"
      ],
      "env": {
        "PIPEDREAM_CLIENT_ID": "${PIPEDREAM_CLIENT_ID}",
        "PIPEDREAM_CLIENT_SECRET": "${PIPEDREAM_CLIENT_SECRET}",
        "PIPEDREAM_PROJECT_ID": "${PIPEDREAM_PROJECT_ID}"
      }
    }
  }
}

Paste under mcpServers. Fully quit and reopen Claude after editing.

CLI or .mcp.jsonshell

# export PIPEDREAM_CLIENT_ID=your_client_id
# export PIPEDREAM_CLIENT_SECRET=your_secret
# export PIPEDREAM_PROJECT_ID=your_project
claude mcp add pipedream -- npx @pipedream/mcp

Run from your repo. Commit .mcp.json to share with your team.

.cursor/mcp.jsonjson

{
  "mcpServers": {
    "pipedream": {
      "command": "npx",
      "args": [
        "@pipedream/mcp"
      ],
      "env": {
        "PIPEDREAM_CLIENT_ID": "${PIPEDREAM_CLIENT_ID}",
        "PIPEDREAM_CLIENT_SECRET": "${PIPEDREAM_CLIENT_SECRET}",
        "PIPEDREAM_PROJECT_ID": "${PIPEDREAM_PROJECT_ID}"
      }
    }
  }
}

Global path: ~/.cursor/mcp.json. Reload window after editing.

.vscode/mcp.jsonjsonc

{
  "servers": {
    "pipedream": {
      "command": "npx",
      "args": [
        "@pipedream/mcp"
      ],
      "env": {
        "PIPEDREAM_CLIENT_ID": "${PIPEDREAM_CLIENT_ID}",
        "PIPEDREAM_CLIENT_SECRET": "${PIPEDREAM_CLIENT_SECRET}",
        "PIPEDREAM_PROJECT_ID": "${PIPEDREAM_PROJECT_ID}"
      }
    }
  }
}

VS Code uses the "servers" key (not "mcpServers").

~/.codeium/windsurf/mcp_config.jsonjson

{
  "mcpServers": {
    "pipedream": {
      "command": "npx",
      "args": [
        "@pipedream/mcp"
      ],
      "env": {
        "PIPEDREAM_CLIENT_ID": "${PIPEDREAM_CLIENT_ID}",
        "PIPEDREAM_CLIENT_SECRET": "${PIPEDREAM_CLIENT_SECRET}",
        "PIPEDREAM_PROJECT_ID": "${PIPEDREAM_PROJECT_ID}"
      }
    }
  }
}

Open via Cascade → hammer icon → Configure.

cline_mcp_settings.jsonjson

{
  "mcpServers": {
    "pipedream": {
      "command": "npx",
      "args": [
        "@pipedream/mcp"
      ],
      "env": {
        "PIPEDREAM_CLIENT_ID": "${PIPEDREAM_CLIENT_ID}",
        "PIPEDREAM_CLIENT_SECRET": "${PIPEDREAM_CLIENT_SECRET}",
        "PIPEDREAM_PROJECT_ID": "${PIPEDREAM_PROJECT_ID}"
      }
    }
  }
}

Open via the Cline sidebar → MCP Servers → Edit.

~/.continue/config.jsonjson

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "@pipedream/mcp"
          ],
          "env": {
            "PIPEDREAM_CLIENT_ID": "${PIPEDREAM_CLIENT_ID}",
            "PIPEDREAM_CLIENT_SECRET": "${PIPEDREAM_CLIENT_SECRET}",
            "PIPEDREAM_PROJECT_ID": "${PIPEDREAM_PROJECT_ID}"
          }
        }
      }
    ]
  }
}

Continue uses modelContextProtocolServers with a transport block.

~/.codex/config.tomlshell

# ~/.codex/config.toml
[mcp_servers.pipedream]
command = "npx"
args = [
  "@pipedream/mcp",
]
env = { PIPEDREAM_CLIENT_ID = "${PIPEDREAM_CLIENT_ID}", PIPEDREAM_CLIENT_SECRET = "${PIPEDREAM_CLIENT_SECRET}", PIPEDREAM_PROJECT_ID = "${PIPEDREAM_PROJECT_ID}" }

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

~/.config/zed/settings.jsonjsonc

{
  "context_servers": {
    "pipedream": {
      "command": {
        "path": "npx",
        "args": [
          "@pipedream/mcp"
        ]
      },
      "env": {
        "PIPEDREAM_CLIENT_ID": "${PIPEDREAM_CLIENT_ID}",
        "PIPEDREAM_CLIENT_SECRET": "${PIPEDREAM_CLIENT_SECRET}",
        "PIPEDREAM_PROJECT_ID": "${PIPEDREAM_PROJECT_ID}"
      }
    }
  }
}

Zed calls them "context_servers". Settings live-reload on save.

ChatGPT → Settings → Connectors (remote URL)json

{
  "name": "Pipedream",
  "transport": "http",
  "url": "https://mcp.pipedream.com"
}

Paste this into Settings → Connectors → Add custom connector. Requires ChatGPT Pro / Team / Enterprise / Edu with Developer mode enabled. ChatGPT supports remote HTTPS MCP servers only — stdio servers must be hosted on a public HTTPS endpoint first.

2
Set required secrets
Set PIPEDREAM_CLIENT_ID, PIPEDREAM_CLIENT_SECRET, PIPEDREAM_PROJECT_ID in your shell environment before launching your MCP client.
3
Try a minimum working prompt
Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.

Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.

Recommend the best MCP servers for [task: e.g. automation & workflows work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-automation-workflows

Compare Pipedream against a real alternative. Swap the second MCP in [brackets] if you want a different match.

Compare Pipedream MCP vs [Zapier MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/pipedream
- top-mcps.com listing for Zapier

Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.

Install the Pipedream MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/pipedream (fetch https://top-mcps.com/mcp/pipedream.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (PIPEDREAM_CLIENT_ID, PIPEDREAM_CLIENT_SECRET, PIPEDREAM_PROJECT_ID) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.

May 27, 2026
Refreshed install snippets and fact sheet; verified for 2026.
Jun 10, 2025
Initial directory listing.

More Automation & Workflows MCPs

Other tools in the same category worth evaluating.

Zapier

Official

Expose 8,000+ Zapier integrations as tools your AI agent can call.

zapierautomationintegrationsworkflow

5 minLow

Make.com

Official

Turn Make.com on-demand scenarios into agent-callable tools — official MCP.

make-comautomationworkflowsintegromat

10 minMedium

Inngest

Official

Built-in MCP for Inngest functions, events, runs, and docs — zero auth, zero config.

inngesteventsworkflowsdev-server

< 1 minLow

Compared with Pipedream

Side-by-side breakdowns for the choices people most often weigh against this MCP.

PipedreamvsMake.com PipedreamvsZapier PipedreamvsInngest Pipedreamvsn8n (MCP archived)

Exploring Top MCPs for Automation & Workflows? See all Automation & Workflows MCPs →

Quick answer

What it does

Best for

Not for

Setup recipe

Install

Set required secrets

Try a minimum working prompt

Tools & permissions

Agent prompt pack

Full details

Frequently asked questions

License?

Self-hosting?

How is OAuth managed?

What changed

More Automation & Workflows MCPs

Zapier

Make.com

Inngest

Compared with Pipedream