# Pipedream MCP ID: 07-pipedream-mcp Page: https://gtmmcps.com/tools/07-pipedream-mcp JSON: https://gtmmcps.com/data/tools/07-pipedream-mcp.json Documentation references: https://gtmmcps.com/docs/07-pipedream-mcp/ Category: MCP Layer MCP support: official Testing: RESEARCHED API access: paid Last checked: 2026-08-24 Endpoint check: docs-only; date: 2026-09-04 Pipedream's existing workflow/integration platform re-exposed as hosted MCP servers, giving an MCP client access to 3,000+ connected apps and 10,000+ pre-built tools via Pipedream Connect. ## MCP links - https://mcp.pipedream.com ## Sources - https://mcp.pipedream.com - https://pipedream.com/docs/connect/mcp - https://github.com/PipedreamHQ/mcp-chat ## Research notes Pipedream is custodial like Composio - it stores end-user credentials server-side rather than passing them through. Could not confirm exact production-tier pricing numbers in this pass (pricing docs page 404'd); marked unknown rather than guessed. GTM apps (Salesforce, HubSpot) were not explicitly named in the fetched docs, only implied by the "3,000+ apps" breadth claim. 2026-09-09 (P6-04 repo sweep): first-party repository recorded at https://github.com/PipedreamHQ/mcp-chat, the org PipedreamHQ (profile site pipedream.com), 192 stars, last push 2026-05-08. It is NOT the server source: the README describes an open-source reference chat app built on Pipedream's MCP server. The npm package @pipedream/mcp ("Pipedream stdio and SSE MCP servers") declares no repository, and a contents read of the PipedreamHQ/pipedream monorepo on 2026-09-09 found no modelcontextprotocol directory under the root or under packages/, so no public server source was found. ## Named capabilities Tool names below are reported by sources. Their presence is not a successful call. - CONFIGURE_COMPONENT: Retrieve configuration values for dynamic properties of a component.; evidence: docs; party: aggregator:pipedream ## CLI evidence Status: none-found Read current vendor documentation before configuring or running commands.