Hosting

hosted

Transport

Streamable HTTP

Endpoint

https://remote.mcp.pipedream.net

Authentication

Pipedream Connect project credentials and connected account authorization.

Requirements

• Pipedream account and project.
• Pipedream OAuth client credentials and project/environment identifiers.
• A stable external user ID in the integrating application.
• An app slug from Pipedream's integration catalog.
• For a user-facing product, an implementation of the Pipedream frontend SDK or Connect Link account authorization flow.

Setup steps

1. Create a Pipedream account and project, then create OAuth client credentials for the project.
2. Store PIPEDREAM_CLIENT_ID, PIPEDREAM_CLIENT_SECRET, PIPEDREAM_PROJECT_ID, and PIPEDREAM_ENVIRONMENT in the integrating application's secret manager.
3. Obtain a short-lived developer bearer token through Pipedream's SDK/API.
4. Connect the client to https://remote.mcp.pipedream.net/v3 and send the documented Authorization, x-pd-project-id, x-pd-environment, x-pd-external-user-id, and x-pd-app-slug headers.
5. Implement end-user account authorization through Pipedream's frontend SDK or Connect Link; the server returns a connection URL when a required app account is missing.
6. List the tools dynamically for the selected app slug and confirm the intended integration is connected.

Publisher documentation reports access to 3,000+ apps/APIs and 10,000+ tools. Tool schemas and operations are selected/discovered at runtime from connected app actions; no universal fixed MCP tool list applies. Development mode is free, but requires a Pipedream project and credentials.

• CONFIGURE_COMPONENT

  Retrieve configuration values for a dynamic component property; observed for an app-scoped Pipedream MCP endpoint.

  01

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

• Actual tools and schemas depend on selected apps/actions and connected accounts.
• Free development mode requires a Pipedream project and API credentials.

• official publisher documentation

  Pipedream documentation describes generated app actions selected per user/server, not a fixed global name list.

• publisher website

  Official Pipedream site.

• official app tool reference

  App-specific MCP example shows a namespaced tool ID (browser_use-create-browser-session), demonstrating that identifiers are integration-specific.

• official documentation

  Current publisher or maintainer documentation reviewed 2026-10-28T19:00:00.000Z.

• official tools list capture

  Pipedream community support includes a raw tools/list response naming CONFIGURE_COMPONENT for an app-scoped Pexels endpoint. This is an observed configured-app tool, not a claim that every Pipedream account sees the same list.

Documentation checked 2026-10-28T19:00:00.000Z. Connection has not been runtime tested.