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:
cp .env.example .env
# Fill in PD client ID/secret, project ID, and environment
pnpm dev:http
PD_SDK_DEBUG=true pnpm dev:http
npx @modelcontextprotocol/inspector
http://localhost:3010/v1/{external_user_id}/{app}
or for SSE Transport:
http://localhost:3010/{external_user_id}/{app}
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=developmentpnpm installpnpm dev:httpPD_SDK_DEBUG=true pnpm dev:httpnpx @modelcontextprotocol/inspectorUse 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.tsSee the logs for the inspector URL and use the inspector to verify MCP tool interactions.
Installation Guide
cp .env.example .env and fill in the details. pnpm install. pnpm dev:http. Optional: debug requests with PD_SDK_DEBUG=true pnpm dev:http. npx @modelcontextprotocol/inspector. http://localhost:3010/v1/{external_user_id}/{app} or the SSE URL: http://localhost:3010/{external_user_id}/{app}. 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
Sponsored
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.
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.
Compare Alternatives
Similar MCP Tools
9 related toolsGraphiti 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 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 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
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.
Playwright MCP
Playwright MCP server. A Model Context Protocol (MCP) server that provides browser automation capabilities using Playwright. This server enables large language models (LLMs) to interact with web pages through structured accessibility snapshots, bypassing the need for screenshots or visually-tuned models. The server is designed to be fast, lightweight, and deterministic, offering LLM-friendly tooling and a rich set of browser automation capabilities via MCP tools. It supports standalone operation, containerized deployments, and integration with a variety of MCP clients (Claude Desktop, VS Code, Copilot, Cursor, Goose, Windsurf, and others).
Sequential Thinking MCP Server
Sequential Thinking MCP Server provides a dedicated MCP tool that guides problem-solving through a structured, step-by-step thinking process. It supports dynamic adjustment of the number of thoughts and allows revision and branching within a controlled workflow, making it ideal for complex analysis and solution hypothesis development. This server is designed to register a single tool, sequential_thinking, and is integrated with common MCP deployment methods (NPX, Docker) as well as editor integrations like Claude Desktop and VS Code for quick setup. The documentation provides exact configuration snippets, usage patterns, and building instructions to help you deploy and use the MCP server effectively, including Codex CLI, NPX, and Docker installation examples.
N8N MCP Server
An MCP (Model Context Protocol) server designed to integrate Claude Desktop, Claude Code, Windsurf, and Cursor with n8n workflows. This MCP enables users to build, test, and orchestrate complex workflows by exposing a set of tools that bridge Claude’s capabilities with n8n’s automation platform. The project emphasizes robust trigger handling, multi-tenant readiness, and progressive documentation to help developers understand how tools map to real-world workflow tasks. It also outlines future tooling integration points (such as getNodeEssentials and getNodeInfo) to further enhance node-structure awareness within MCP-powered automations.
Hugging Face MCP Server
Hugging Face Official MCP Server connects your large language models (LLMs) to the Hugging Face Hub and thousands of Gradio AI Applications, enabling seamless MCP (Model Context Protocol) integration across multiple transports. It supports STDIO, SSE (to be deprecated but still commonly deployed), StreamableHTTP, and StreamableHTTPJson, with the Web Application allowing dynamic tool management and status updates. This MCP server is designed to be run locally or in Docker, and it provides integrations with Claude Desktop, Claude Code, Gemini CLI (and its extension), VSCode, and Cursor, making it easy to configure and manage MCP-enabled tools and endpoints. Tools such as hf_doc_search and hf_doc_fetch can be enabled to enhance document discovery, and an optional Authenticate tool can be included to handle OAuth challenges when called.
Shadcn UI MCP Server v4
Shadcn UI v4 MCP Server is an advanced MCP (Model Context Protocol) server designed to give AI assistants comprehensive access to shadcn/ui v4 components, blocks, demos, and metadata. It enables multi-framework support (React, Svelte, Vue, and React Native) with fast, cache-friendly access to component source code, demos, and directory structures, empowering AI-driven development workflows. The project emphasizes production-readiness with Docker Compose, SSE transport for multi-client deployments, and smart caching to optimize GitHub API usage while providing rich metadata and usage patterns for rapid prototyping and learning across frameworks.