by Pipedream
Updated September 11, 2026
MCP100 verdict
Not currently recommended. Excellent integration breadth and managed auth, but the blast radius of connected accounts is too broad for Selected without a narrowly scoped deployment.
MCP100 Assessment
Editorial verdict
Reviewed September 11, 2026
Task Fit
Mapped
Team productivity
Trust
Status warning
The reviewed current developer docs identify https://remote.mcp.pipedream.net as the hosted server. Do not preserve an unverified /v3 suffix from older discovery evidence.
Maintenance
Date unavailable
No dated repository or package update is currently stored.
Popularity
Signals unavailable
No independently comparable adoption metric is currently stored.
Evidence scope
No MCP-specific repository metric is stored
No MCP-specific package metric is stored
Stars observation date unavailable · Downloads observation date unavailable
Publisher activity observed September 11, 2026
Current source snapshot
Source relationship: First-party MCP
Reviewed September 11, 2026
Evidence-backed setup
Choose your MCP client. A client connects to the MCP server; the language model is selected inside that client. Only stored, source-backed configurations are shown.
Transport not recorded
No sufficient client-specific setup evidence has been stored from the publisher or client documentation.
Publisher-documented setup is not the same as MCP100 execution testing. “MCP100 logic checked” means the stored configuration shape was reviewed, not that third-party MCP software was run.
Evidence checked 2026-09-11T00:00:00.000Z
Type-appropriate, source-backed setup for this mcp server profile.
Loading optional publisher installation details…
No complete evidence-backed client setup steps are currently stored. Optional publisher documentation may provide additional context below.
Capability
Excellent integration breadth and managed auth, but the blast radius of connected accounts is too broad for Selected without a narrowly scoped deployment.
Dynamic hosted tool catalog across connected third-party apps; do not materialize all tools into the static detail page.
Dynamic hosted tool catalog across connected third-party apps; do not materialize all tools into the static detail page.
Not measured yet
Estimated token footprint of the MCP tool schemas exposed to the agent.
Reviewed access
Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.
Related reviewed MCPs
Connect supported AI clients to Jira and Confluence.
Choose this instead if
Choose Atlassian Remote MCP instead if searching and summarizing Jira and Confluence knowledge.
Connect supported AI clients to Jira and Confluence, with a documented Rovo MCP v2 upgrade path for additional supported Atlassian apps.
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
Choose this instead if
Choose Apify MCP Server instead if running Apify Store Actors and retrieving their datasets through a hosted or local MCP connection.
Recommended when a team already uses Apify and wants an assistant to discover and run Actors for web extraction and automation.
A production-ready Model Context Protocol (MCP) server that bridges Ghidra's powerful reverse engineering capabilities with modern AI tools and automation frameworks.
Choose this instead if
Choose Ghidra MCP Server instead if querying decompilation, symbols, references, functions, and analysis state inside Ghidra.
Recommended for controlled reverse-engineering work where an agent may inspect and modify an open Ghidra project.
Pipedream is listed as First-party MCP in MCP100’s current evidence.
Current official resources:
Original product, capability, tool, and usage documentation from the MCP publisher. Installation sections appear under Install & Agents.
Title: Develop with Pipedream MCP - Pipedream
URL Source: https://pipedream.com/docs/connect/mcp/developers
Markdown Content: Add Pipedream MCP to your app or agent to make tool calls on behalf of your users to 3,000+ APIs and 10,000+ tools.
Pipedream Connect includes built-in user authentication for more than APIs via MCP, which means you don’t need to build any authorization flows or deal with token storage and refresh in order to make authenticated requests on behalf of your users.
Use Pipedream MCP with popular AI frameworks and LLMs:
external_user_id
app
To use either the remote or self-hosted MCP server, you’ll need:
Your application authenticates with Pipedream using client credential OAuth. See below for details.
One of the core features of Pipedream Connect and the MCP server is the ability for your users to easily connect their accounts without having to build any of the authorization flow or handle token storage.You can handle account connections in one of two ways in your app:
Pipedream provides + APIs as MCP servers. Each server corresponds to an app integration (like Notion, Gmail, or Slack) and has its own specific set of tools.For detailed information on discovering apps and enabling automatic app discovery, check out app discovery section.
When a tool call fails, Pipedream’s MCP server returns a result with isError: true, following the MCP spec for tool execution errors. This lets the LLM see the error and decide how to respond, rather than surfacing it as a protocol-level error.The error result includes the same error object with an attribution field that’s returned when running actions, which classifies where the error originated (for example, in the tool’s code, the upstream API, or the network layer). See error responses for the full list of attribution origins and details on how attribution works.
Publish custom tools to your Pipedream workspace to use them with Pipedream’s MCP server. This lets you add custom and unique functionality that may not be available in the public registry.
From the publisher README
Original client setup and configuration retained from the publisher documentation.
Set the following environment variables:
Learn more about environments in Pipedream Connect.
The Pipedream MCP server supports both SSE and streamable HTTP transport types dynamically, with no configuration required by the developer or MCP client.
To authenticate requests to Pipedream’s MCP server, you need to include an access token with every HTTP request. Here’s how to get it:
| Header | Query Param | Value | Required? |
|---|---|---|---|
x-pd-project-id | projectId | proj_xxxxxxx | Yes |
x-pd-environment | environment | development | production |
x-pd-external-user-id | externalUserId | <your-users-id> | Yes |
x-pd-app-slug | app | linear, notion, etc | Yes |
x-pd-account-id | accountId | apn_xxxxxxx | No |
The MCP inspector can be helpful when debugging tool calls.
Enter the server URL:
x-pd-oauth-app-idoauthAppId |
oa_xxxxxxx |
| No |
x-pd-registry | registry | public | private |