Pipedream MCP Server Details

Pipedream MCP Server is a reference implementation for self-hosting a Model Context Protocol (MCP) server. It showcases how to manage and serve MCP-based apps and tools in your own environment, providing you with a way to run MCP servers locally or within your organization. Note that this MCP server is a reference implementation and is no longer actively maintained; for production workloads, Pipedream recommends using the remote MCP server, which offers hosted reliability and scaling. The server supports two primary modes and integrates with Pipedream Connect for authentication and API management, enabling automatic app discovery and credential storage with enterprise-grade security.

Use Case

This MCP server allows you to run your own MCP server to manage apps and tools within your own app or company. It supports app-specific endpoints and a dynamic mode that powers tools on sites like chat.pipedream.com. Use cases include connecting accounts, configuring parameters, making API requests via MCP tools, and handling OAuth and credential storage. The server can be run locally or hosted yourself and exposes Streamable HTTP Transport and SSE Transport for client interactions. Example usage from the docs includes running the server, starting with environment configuration, and inspecting requests with the MCP Inspector. Example commands:

  • Copy and configure environment:

  • cp .env.example .env
    # Fill in PD client ID/secret, project ID, and environment
  • Start the server with Streamable HTTP Transport:

  • pnpm dev:http
  • Debug requests/responses (optional):

  • PD_SDK_DEBUG=true pnpm dev:http
  • Run the inspector:

  • npx @modelcontextprotocol/inspector
  • Access Streamable HTTP Transport URL:

  • http://localhost:3010/v1/{external_user_id}/{app}
    or for SSE Transport:
    http://localhost:3010/{external_user_id}/{app}
  • Stdio Transport setup (inspector):

  • npx @modelcontextprotocol/inspector bun src/stdio.ts

    These commands illustrate how to configure and run the MCP server, inspect interactions, and use both HTTP and SSE transport modes. The documentation also notes that you can fetch the list of MCP tools via the Stdio transport by clicking "List Tools".

    Examples & Tutorials

    PIPEDREAM_CLIENT_ID=your_client_id
    PIPEDREAM_CLIENT_SECRET=your_client_secret
    PIPEDREAM_PROJECT_ID=your_project_id
    PIPEDREAM_PROJECT_ENVIRONMENT=development

    pnpm install

    pnpm dev:http

    PD_SDK_DEBUG=true pnpm dev:http

    npx @modelcontextprotocol/inspector

    Use http://localhost:3010/v1/{external_user_id}/{app} for Streamable HTTP Transport or http://localhost:3010/{external_user_id}/{app} for SSE Transport.

    npx @modelcontextprotocol/inspector bun src/stdio.ts

    See the logs for the inspector URL and use the inspector to verify MCP tool interactions.

    Installation Guide

  • Copy environment configuration: cp .env.example .env and fill in the details.

  • Install dependencies: pnpm install.

  • Start the server with Streamable HTTP Transport: pnpm dev:http. Optional: debug requests with PD_SDK_DEBUG=true pnpm dev:http.

  • Run the MCP Inspector: npx @modelcontextprotocol/inspector.

  • Access the Streamable HTTP Transport URL: http://localhost:3010/v1/{external_user_id}/{app} or the SSE URL: http://localhost:3010/{external_user_id}/{app}.

  • For Stdio Transport, run: npx @modelcontextprotocol/inspector bun src/stdio.ts and check logs for the inspector URL.
  • Frequently Asked Questions

    Is this your MCP?

    Claim ownership and get verified badge

    Repository Stats

    Sponsored

    Ad Space Available
    Important Notes

    This MCP server is a reference implementation for self-hosting and is not actively maintained. For production use, Pipedream strongly recommends using the remote MCP server. The reference implementation may not be fully documented, and there are two server usage modes: App-specific endpoints and a Dynamic mode that powers tools on chat.pipedream.com. The SSE interface accepts two route parameters: external_user_id and app.

    Prerequisites

    Sign up for Pipedream, create a project, and create a Pipedream OAuth client. You will need Pipedream API credentials to run the MCP server. Environment variables must be set in a .env file, including PD_CLIENT_ID, PD_CLIENT_SECRET, PD_PROJECT_ID, and PD_PROJECT_ENVIRONMENT as shown in the docs.

    Details
    Last Updated1/1/2026
    SourceGitHub

    Compare Alternatives

    Similar MCP Tools

    9 related tools
    Skyvern MCP

    Skyvern MCP

    Skyvern is the complete browser MCP for AI agents. 75+ tools for clicking, filling forms, extracting structured data, logging in with 2FA, uploading files, drag-and-drop, running JavaScript, inspecting network traffic, multi-tab browsing, and building reusable cached workflows. First workflow run uses AI; subsequent runs replay a cached script with zero LLM calls.

    pageguard-mcp

    pageguard-mcp

    pageguard-mcp is an MCP (Model Context Protocol) server that exposes PageGuard privacy compliance scanning as a set of tools for AI coding assistants. It enables seamless integration with Claude Code, Cursor, Windsurf, ChatGPT, and any MCP-compatible environment. The server supports local scans, live URL scans, and AI-generated privacy-related documents, helping developers identify tracking technologies, cookies, and third-party data processing, while also producing tailored privacy policies and compliance materials. With its straightforward MCP configuration and free local scanning capability, pageguard-mcp is designed to empower teams to maintain privacy compliance across their projects and websites.

    Prop Firm Deal Finder

    Prop Firm Deal Finder (PFDF) is a free MCP server that gives AI assistants real-time access to live discount codes across 20+ proprietary trading firms. It provides 6 tools: get_deals (all current discounts), search_firms (search by name/asset class), compare_firms (side-by-side comparison of challenges), find_cheapest (cheapest challenge by account size with PFDF code applied), get_firm_details (15+ data points per firm), and get_discount_code (universal PFDF code). Covers firms like Topstep, Apex Trader Funding, MyFundedFutures, FTMO, The Funded Trader, and 14 more. No API key required. Install via npx propfirmdealfinder-mcp-server or connect remotely at https://web-production-6607c.up.railway.app/mcp

    mcp-server-with-spring-ai

    mcp-server-with-spring-ai

    mcp-server-with-spring-ai is a Spring Boot integrated MCP (Model Context Protocol) server example that showcases how to expose executable tools from an MCP server to clients (including LLMs) and how to wire a MCP client to consume those tools. The documentation explains MCP at a high level, outlines the three-layer MCP Java SDK architecture (Client/Server Layer, Session Layer, Transport Layer), and demonstrates two sample tools implemented in SellerAccountTools. This repo emphasizes how an MCP server can connect to external data sources (e.g., a PostgreSQL DB) and expose tools that an AI model can invoke to retrieve data, with the example illustrating tool invocation and automatic tool selection by prompts.

    OpenClaw MCP Server

    OpenClaw MCP Server

    OpenClaw MCP Server is a secure Model Context Protocol (MCP) bridge that connects Claude.ai with a self-hosted OpenClaw assistant, enabling OAuth2 authentication and safe, controlled communication between the Claude AI ecosystem and your local or hosted OpenClaw deployment. This MCP server acts as an orchestration layer that exposes MCP tools to Claude.ai, manages authentication, and enforces security boundaries like CORS and transport options. It is designed to be deployed via Docker or run locally, with detailed installation, configuration, and security guidance provided in the documentation. By serving as a bridge, it enables Claude.ai to delegate tasks to your OpenClaw bot while preserving control over data flow and access controls, in line with MCP specifications and best security practices.

    Graphiti MCP Server

    Graphiti MCP Server

    Graphiti MCP Server is an experimental implementation that exposes Graphiti's real-time, temporally-aware knowledge graph capabilities through the MCP (Model Context Protocol) interface. It enables AI agents and MCP clients to interact with Graphiti's knowledge graph for structured extraction, reasoning, and memory across conversations, documents, and enterprise data. The server supports multiple backends (FalkorDB by default and Neo4j), a variety of LLM providers (OpenAI, Anthropic, Gemini, Groq, Azure OpenAI), and multiple embedder options, all accessible via an HTTP MCP endpoint at /mcp/ for broad client compatibility. It also includes queue-based asynchronous episode processing, rich entity types for structured data, and flexible configuration through config.yaml, environment variables, or CLI arguments.

    Context7 MCP Server

    Context7 MCP Server

    Context7 MCP Server delivers up-to-date, code-first documentation and examples for LLMs and AI code editors by pulling content directly from the source. It supports multiple MCP clients and exposes tools that help you resolve library IDs and retrieve library documentation, ensuring prompts use current APIs and usage patterns. The repository provides installation and integration guides for Cursor, Claude Code, Opencode, and other clients, along with practical configuration samples and OAuth options for remote HTTP connections. This MCP server is designed to keep prompts in sync with the latest library docs, reducing hallucinations and outdated code snippets.

    TrendRadar MCP

    TrendRadar MCP

    TrendRadar MCP is an AI-driven Model Context Protocol (MCP) based analysis server that exposes a suite of specialized tools for cross-platform news analysis, trend tracking, and intelligent push notifications. It integrates with TrendRadar’s multi-platform data aggregation (RSS and trending topics) and provides advanced AI-powered insights, sentiment analysis, and cross-platform correlation. The MCP server enables developers to query, analyze, and compare news across platforms using a consistent toolset, with ongoing updates that expand capabilities such as RSS querying, date parsing, and multi-date trend analysis. This documentation references the MCP module updates, tool additions, and architecture changes that enhance extensibility, cross-platform data handling, and AI-assisted reporting.

    ChainAware Behavioural Prediction MCP

    ChainAware Behavioural Prediction MCP

    The ChainAware Behavioural Prediction MCP is an MCP-based server that provides AI-powered tools to analyze wallet behaviour prediction, fraud detection, and rug pull prediction. Designed for Web3 security and DeFi analytics, it enables developers and platforms to integrate risk assessment, predictive wallet behavior insights, and rug-pull detection through MCP-compatible clients. The server exposes three specialized tools and uses Server-Sent Events (SSE) for real-time responses, helping safeguard DeFi users, monitor liquidity risks, and score wallet or contract trustworthiness. Access to production endpoints is API-key gated, reflecting a private backend architecture that supports secure, scalable risk analytics across wallets, contracts, and pools.