App discovery
Search and list available integrations programmatically through SDK or REST API.
Documentation ↗MCP server / integration platform / source-linked
Pipedream MCP
Pipedream MCP exposes app-specific hosted MCP servers and custom tools for products that need end-user account connections. Its current developer endpoint supports both SSE and Streamable HTTP. Requests carry a project, environment, external user, and app slug, allowing the server to resolve the right connected account for each end user.
Before you choose.
Identify the implementation and the job it supports.
Pipedream MCP exposes app-specific hosted MCP servers and custom tools for products that need end-user account connections. Its current developer endpoint supports both SSE and Streamable HTTP. Requests carry a project, environment, external user, and app slug, allowing the server to resolve the right connected account for each end user.
Setup and connection.
The documented interface, authentication and installation path.
- Connection / transport
- SSE and Streamable HTTP
- Authentication
- Bearer access token from the Pipedream SDK/client-credentials flow plus required project, environment, external-user, and app headers.
Create a Pipedream project/app, obtain an access token, choose the app slug, and call https://remote.mcp.pipedream.net/v3 with the documented headers. Keep external_user_id stable per user.
Setup reference ↗Documented setup example. Review the source and credentials before running; this command was not executed for this article.
https://remote.mcp.pipedream.net/v3?externalUserId=USER_ID&app=APP_SLUGWhat it actually exposes.
Concrete capabilities with maintainer sources.
Per-user connected accounts
Bind requests to external_user_id and the user’s connected app account.
Documentation ↗Custom tools
Publish workspace custom tools and expose them through the MCP server alongside public app integrations.
Documentation ↗Evidence and method.
What was checked and what was not tested.
HOW
Source method
Public maintainer documentation and repositories. This is not a hands-on product review.
WHEN
Last checked 2026-10-01
Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.
Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.
Community signals.
Concrete reports from public community discussions, kept separate from product documentation.
How to give Claude full control in Google Drive?
讨论把内置 Drive connector 与自建 MCP、Apps Script、Pipedream 和 Drive for Desktop 进行比较。用户明确需要重命名、移动、删除等完整文件管理，而内置连接器主要覆盖搜索、读取、上传和创建文件。建议在隔离文件夹中先验证写入和删除行为。
“The built-in Drive connector isn't really for full file management.”Open community source ↗
Signal: managed oauth vs cost
A user valued Pipedream's OAuth because it avoids collecting credentials for every tool, while worrying about eventual cost as usage grows.
“I liked the Pipedream OAuth but realise this will cost eventually.”Open community source ↗
Signal: multi account routing limit
Support explained that selecting a specific connection was not available when a user had multiple accounts for the same app, creating ambiguity for multi-account workflows.
“Today you can’t define the specific accountId in the case of multiple accounts.”Open community source ↗
Signal: oauth client compatibility
A Goose user configuring the hosted Pipedream endpoint saw an invalid_request OAuth error and three duplicate browser tabs during connection.
“three duplicate browser tabs open displaying an OAuth resource error”Open community source ↗
Community evidence is anecdotal and may reflect one setup, version or account. It is included for discovery and risk-sensing, not as a representative rating or independent benchmark. Verify the current official documentation before acting on a report.
Try a specific task.
A bounded evaluation you can reproduce in your own environment.
End-user app action
Suggested evaluation, not an observed test result.
- Create a project environment and map your product user to external_user_id.
- Discover the target app slug and ask the agent to list available actions.
- Require confirmation before the client executes a write and log the attributed result.
What to inspect: A user-scoped action request that can be traced back to the project, app, and external account. Proposed workflow; not tested by clawbot.ai.
Workflow reference ↗Permissions and limitations.
Read these constraints before granting access.
Every request needs project, environment, external-user, and app identity; missing or mismatched headers are a setup boundary, not a server feature failure.
Boundary reference ↗OAuth/account connection and action execution remain application-dependent; Pipedream returns attributed tool errors rather than hiding the upstream failure.
Boundary reference ↗Decide by workflow.
Make the expected output explicit before you connect.
A user-scoped action request that can be traced back to the project, app, and external account. Proposed workflow; not tested by clawbot.ai.
Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.
Compare the alternatives.
Specific reasons to choose another route, with the tradeoff shown.
| Alternative | Choose it when | Tradeoff |
|---|---|---|
| Zapier MCP | Choose for consumer-style setup with a single endpoint and Zapier-managed app credentials. | Pipedream is more developer-oriented and supports custom tools; Zapier is simpler for existing connections. Documentation ↗ |
| Composio MCP | Choose for session-level tool policies and a hosted per-user endpoint. | Composio has richer session policy controls; Pipedream emphasizes app discovery and identity headers. Documentation ↗ |
Questions before setup.
Answers specific to this implementation.
Which transports are supported?
The remote Pipedream MCP supports SSE and Streamable HTTP dynamically.
Documentation ↗
Why is external_user_id required?
It couples requests to the end user and their connected accounts, so actions resolve against the correct user context.
Documentation ↗
Source trail.
Maintainer documentation used in this record.