Pipedream

by PipedreamHQ

Community Developer Tools 12k likes

Pipedream's MCP server gives an agent OAuth-managed access to 3,000-plus APIs and 10,000-plus pre-built actions, without ever exposing credentials to the model.

Connect via MCP Inspector

npx @modelcontextprotocol/inspector

Source: https://github.com/PipedreamHQ/pipedream

About

Pipedream Connect exposes its existing action registry (the same one behind its no-code workflow builder) as an MCP endpoint at remote.mcp.pipedream.net/v3, scoped per request by headers or query params (x-pd-project-id, x-pd-external-user-id, x-pd-app-slug) rather than a fixed tool list you install once. Point the endpoint at app=slack and an agent gets Slack's tools; point it at app=notion and it gets Notion's. Each user's OAuth tokens are stored and refreshed by Pipedream and never handed to the model or your client-side code.

Getting an access token is a few lines with the official SDK (PipedreamClient in TypeScript, Pipedream in Python) using a project's client ID, secret, and project ID, or a direct OAuth client-credentials POST to api.pipedream.com if you'd rather skip the SDK. For a quick look before wiring anything into a real client, the MCP Inspector (npx @modelcontextprotocol/inspector) can connect straight to the endpoint URL with your externalUserId and app slug filled in.

Key features

  • One MCP endpoint fronts 3,000+ integrated apps and 10,000+ pre-built tools
  • Per-user OAuth credentials are stored and refreshed server-side, never exposed to the model or client
  • Scoped to a specific app per request via x-pd-app-slug / app query param
  • Official SDKs in TypeScript, Python, Java, and Go for minting access tokens
  • Revocable, user-isolated access controls for each connected account
  • Same action registry that powers Pipedream's no-code workflow builder

Use cases

  • Let an agent post to Slack or create a Notion page using a user's own connected account, without the agent ever seeing an API key
  • Build a support tool that files tickets and updates CRM records across several connected SaaS apps from one MCP integration
  • Give a chat assistant the ability to schedule calendar events or send email through a user's own Google account
  • Prototype an integration quickly with MCP Inspector before wiring app-scoped access into a production client

Available tools

App-scoped action tools

Each connected app (Slack, GitHub, Google Sheets, etc.) surfaces its own set of pre-built action tools once selected via the app-slug parameter.

PipedreamClient.rawAccessToken

SDK call that mints a scoped access token for a project, used to authenticate MCP requests.

Frequently asked questions

Does the AI model ever see my users' API keys or OAuth tokens?

No. Pipedream stores and refreshes credentials server-side; the model only ever calls tools, it never receives the underlying secrets.

Do I get every app's tools at once, or do I have to pick one?

Requests are scoped per app via the app-slug parameter (or x-pd-app-slug header), so you point the endpoint at the specific app (e.g. slack or notion) you want tools for.