Pipedream MCP Server

⚠️ 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.

Recommended: Use Pipedream's Remote MCP Server

For the best experience, use Pipedream's hosted MCP server which provides:

• 2,800+ APIs and 10,000+ tools through a single server
• Built-in authentication: no manual token management required
• Multiple tool modes: sub-agent and full configuration
• Automatic app discovery
• Enterprise-grade reliability and security

🚀 Get started: Pipedream MCP Documentation

🎮 Try it now: Check out our open source chat app at chat.pipedream.com

---

Self-Hosting (Reference Implementation)

This reference implementation shows how you can:

• Run the servers locally with npx @pipedream/mcp
• Host the servers yourself to use them within your app or company

See the consumer-facing MCP server in action at mcp.pipedream.com and check out a demo of the developer-facing product at chat.pipedream.com.

We 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.

For production use, we strongly recommend using our remote MCP server instead.

⭐ Reference Implementation Features

• Run your own MCP server for over 2,800 apps and APIs
• Manage servers for your users, in your own app
• Connect accounts, configure params, and make API requests, all via tools
• Fully-managed OAuth and credential storage (see security docs)

🚀 Getting Started

Pipedream's MCP servers use the Pipedream Connect API to manage auth and make API requests. To run an MCP server, you'll need a Pipedream project and Pipedream API credentials.

1. Sign up for Pipedream
2. Create a project. Any accounts connected via MCP will be stored here.
3. Create a Pipedream OAuth client
4. Set the environment variables (See .env.example) (directly in your shell session, dot files, etc.):

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

Pipedream concepts to understand

If you're running MCP servers for your app, you'll likely want to use the SSE interface. The SSE server accepts two route params:

1. 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 for more detail.
2. app — The app's "name slug" (the unique identifier for the app), found in the Authentication section of any Pipedream app. For example, the app slug for Slack is slack.

If 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 for more detail.

Server overview

There are two ways to use this MCP server.

1 - App specific /{external_user_id}/{app} This is currently available at mcp.pipedream.com. You can use an endpoint for each app. All the tools available for that app will be available at that endpoint.

2 - Dynamic /{external_user_id} This is an experimental version, since it relies on tools being able to update dynamically. We use this server to power the tools on chat.pipedream.com.

[!NOTE] > Check out the docs to learn more about enabling app discovery with the MCP server.

Development

cp .env.example .env and fill in the details of your dev project.

pnpm install

Start the server with Streamable HTTP Transport

pnpm dev:http

You can use the optional env var PD_SDK_DEBUG to print out all the requests and responses going to the Connect API

PD_SDK_DEBUG=true pnpm dev:http

Then run the inspector:

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.

These URLs can also be used by other clients (e.g. Cursor).

Stdio Transport setup

Stdio has only been tested with the MCP Inspector.

npx @modelcontextprotocol/inspector bun src/stdio.ts

See the logs for the inspector URL.

Ensure the left side of the inspector matches this:

Then press "List Tools" to fetch the list of MCP tools.

License

Pipedream Source Available License Version 1.0 - See https://github.com/PipedreamHQ/pipedream/blob/master/LICENSE