Pipedream MCP Server

1# Pipedream MCP Server
2 
3> **⚠️ Important Notice**: This MCP server is a **reference implementation only** and is no longer actively maintained. For production use, we recommend using Pipedream's **remote MCP server** instead.
4 
5## Recommended: Use Pipedream's Remote MCP Server
6 
7For the best experience, use Pipedream's hosted MCP server which provides:
8 
9- **2,800+ APIs and 10,000+ tools** through a single server
10- **Built-in authentication**: no manual token management required
11- **Multiple tool modes**: sub-agent and full configuration
12- **Automatic app discovery**
13- **Enterprise-grade reliability and security**
14 
15**🚀 Get started**: [Pipedream MCP Documentation](https://pipedream.com/docs/connect/mcp/developers)
16 
17> **🎮 Try it now**: Check out our [open source chat app](https://github.com/PipedreamHQ/mcp) at [chat.pipedream.com](https://chat.pipedream.com/)
18 
19---
20 
21## Self-Hosting (Reference Implementation)
22 
23This reference implementation shows how you can:
24 
25- [Run the servers locally](#running-the-server-via-npx) with `npx @pipedream/mcp`
26- [Host the servers yourself](#hosting-your-own-server) to use them within your app or company
27 
28See the consumer-facing MCP server in action at [mcp.pipedream.com](https://mcp.pipedream.com) and check out a demo of the developer-facing product at [chat.pipedream.com](https://chat.pipedream.com).
29 
30We published this code as a reference, so you can better understand how to use Pipedream Connect for such an application. This is a reference implementation specifically for self-hosting the server and may not be fully documented.
31 
32**For production use, we strongly recommend using our [remote MCP server](https://pipedream.com/docs/connect/mcp/developers) instead.**
33 
34## ⭐ Reference Implementation Features
35 
36- Run **your own MCP server** for [over 2,800 apps and APIs](https://mcp.pipedream.com)
37- Manage servers **for your users**, in your own app
38- Connect accounts, configure params, and make API requests, all via tools
39- Fully-managed OAuth and credential storage ([see security docs](https://pipedream.com/docs/privacy-and-security/#third-party-oauth-grants-api-keys-and-environment-variables))
40 
41## 🚀 Getting Started
42 
43Pipedream's MCP servers use the [Pipedream Connect API](https://pipedream.com/docs/connect/) to manage auth and make API requests. To run an MCP server, you'll need a Pipedream project and Pipedream API credentials.
44 
451. [Sign up for Pipedream](https://pipedream.com/auth/signup)
462. [Create a project](https://pipedream.com/docs/workflows/projects/#creating-projects). Any accounts connected via MCP will be stored here.
473. [Create a Pipedream OAuth client](https://pipedream.com/docs/rest-api/auth/#creating-an-oauth-client)
484. Set the environment variables (See `.env.example`) (directly in your shell session, dot files, etc.):
49 
50```bash
51PIPEDREAM_CLIENT_ID=your_client_id
52PIPEDREAM_CLIENT_SECRET=your_client_secret
53PIPEDREAM_PROJECT_ID=your_project_id
54PIPEDREAM_PROJECT_ENVIRONMENT=development
55```
56 
57### Pipedream concepts to understand
58 
59If you're running MCP servers for your app, you'll likely want to use the [SSE interface](#sse). The SSE server accepts two route params:
60 
611. `external_user_id` — This is your user’s ID, in your system — whatever you use to uniquely identify them. Any requests made to that route are coupled to that end user, and would use the auth Pipedream stores for that user. [See the docs](https://pipedream.com/docs/connect/api/#external-users) for more detail.
622. `app` — The app's "name slug" (the unique identifier for the app), found in the **Authentication** section of [any Pipedream app](https://pipedream.com/apps). For example, the app slug for [Slack](https://pipedream.com/apps/slack) is `slack`.
63 
64If your user `123` wants to connect to the `slack` MCP server, your MCP client would make a request to the `/123/slack` route. [See the SSE docs below](#sse) for more detail.
65 
66## Server overview
67 
68There are two ways to use this MCP server.
69 
701 - App specific
71`/{external_user_id}/{app}`
72This is currently available at [mcp.pipedream.com](https://mcp.pipedream.com). You can use an endpoint for each app.
73All the tools available for that app will be available at that endpoint.
74 
752 - Dynamic
76`/{external_user_id}`
77This is an experimental version, since it relies on tools being able to update dynamically.
78We use this server to power the tools on [chat.pipedream.com](https://chat.pipedream.com).
79 
80> [!NOTE] > [Check out the docs](https://pipedream.com/docs/connect/mcp/app-discovery) to learn more about enabling app discovery with the MCP server.
81 
82## Development
83 
84`cp .env.example .env` and fill in the details of your dev project.
85 
86```bash
87pnpm install
88```
89 
90### Start the server with Streamable HTTP Transport
91 
92```bash
93pnpm dev:http
94```
95 
96You can use the optional env var `PD_SDK_DEBUG` to print out all the requests and responses going to the Connect API
97 
98```bash
99PD_SDK_DEBUG=true pnpm dev:http
100```
101 
102Then run the inspector:
103 
104```bash
105npx @modelcontextprotocol/inspector
106```
107 
108Use `http://localhost:3010/v1/{external_user_id}/{app}` for Streamable HTTP Transport or `http://localhost:3010/{external_user_id}/{app}` for SSE Transport.
109 
110These URLs can also be used by other clients (e.g. Cursor).
111 
112### Stdio Transport setup
113 
114Stdio has only been tested with the MCP Inspector.
115 
116```bash
117npx @modelcontextprotocol/inspector bun src/stdio.ts
118```
119 
120See the logs for the inspector URL.
121 
122Ensure the left side of the inspector matches this:
123 
124![Screenshot 2025-03-12 at 1 05 37 PM](https://github.com/user-attachments/assets/cc650999-353c-45da-add8-7d8de867d6ed)
125 
126Then press "List Tools" to fetch the list of MCP tools.
127 
128## License
129 
130Pipedream Source Available License Version 1.0 - See https://github.com/PipedreamHQ/pipedream/blob/master/LICENSE
131