Mentioned as a potential data store for session persistence when customizing the implementation, suggesting the server can be extended to use Redis for data storage.
Provides tools for connecting to Slack workspaces and making API requests, enabling interaction with Slack channels, messages, users, and other Slack resources.
This is a reference implementation of the Pipedream MCP server. You can run your own MCP server for over 2,500 apps and APIs and is powered by Pipedream Connect.
You can:
npx @pipedream/mcpSee the server in action at mcp.pipedream.com and 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 still a work in progress, and not fully documented. Please reach out to us if you have any questions.
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.
.env.example) (directly in your shell session, dot files, etc.):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:
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.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.
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
The code for the dynamic MCP server is available in this repo but you will not yet be able to run it locally since it relies on an internal db.
Please let us know if you'd like to run this yourself.
DockerfileIf you have Docker installed locally, you can build and run the container:
This exposes a generic MCP server at http://localhost:3010/:external_user_id/:app.
cp .env.example .env and fill in the details of your dev project.
You can use the optional env var PD_SDK_DEBUG to print out all the requests and responses going to the Connect API
Then run the 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 has only been tested with the MCP Inspector.
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.
Pipedream Source Available License Version 1.0 - See https://github.com/PipedreamHQ/pipedream/blob/master/LICENSE
This server cannot be installed
hybrid server
The server is able to function both locally and remotely, depending on the configuration or use case.
Run your own MCP server for over 2,500 apps and APIs.