Title: Develop with Pipedream MCP - Pipedream
URL Source: https://pipedream.com/docs/connect/mcp/developers
Markdown Content:
- Connect
- MCP
Add Pipedream MCP to your app or agent to make tool calls on behalf of your users to 3,000+ APIs and 10,000+ tools.
Overview
Pipedream Connect includes built-in user authentication for more than APIs via MCP, which means you don’t need to build any authorization flows or deal with token storage and refresh in order to make authenticated requests on behalf of your users.
Examples
AI Frameworks
Use Pipedream MCP with popular AI frameworks and LLMs:
Key Pipedream concepts to understand
external_user_id
- This is your user’s ID, in your system: whatever you use to uniquely identify them
- Requests made for that user ID are coupled to that end user and their connected accounts (learn more)
app
- The app’s “name slug” (the unique identifier for the app)
- Check out the app discovery docs to learn how to discover and use available apps
Prerequisites
To use either the remote or self-hosted MCP server, you’ll need:
- A Pipedream account
- A Pipedream project. Accounts connected via MCP will be stored here.
- Pipedream OAuth credentials
Authentication
Developer authentication
Your application authenticates with Pipedream using client credential OAuth. See below for details.
User account connections
One of the core features of Pipedream Connect and the MCP server is the ability for your users to easily connect their accounts without having to build any of the authorization flow or handle token storage.You can handle account connections in one of two ways in your app:
Add a button in your UI
- Use Pipedream’s frontend SDK to let users connect their account directly in your UI
- You can see an example of this when you connect any account in mcp.pipedream.com
Return a link
- Use Connect Link to let your users connect their account in a new browser tab
- This is handled automatically by Pipedream’s MCP server and there’s no additional implementation required
- If a user doesn’t have a connected account that’s required for a given tool call, the server will return a URL in the tool call response:
Discover available integrations
Pipedream provides + APIs as MCP servers. Each server corresponds to an app integration (like Notion, Gmail, or Slack) and has its own specific set of tools.For detailed information on discovering apps and enabling automatic app discovery, check out app discovery section.
Error handling
When a tool call fails, Pipedream’s MCP server returns a result with isError: true, following the MCP spec for tool execution errors. This lets the LLM see the error and decide how to respond, rather than surfacing it as a protocol-level error.The error result includes the same error object with an attribution field that’s returned when running actions, which classifies where the error originated (for example, in the tool’s code, the upstream API, or the network layer). See error responses for the full list of attribution origins and details on how attribution works.
Using custom tools
Publish custom tools to your Pipedream workspace to use them with Pipedream’s MCP server. This lets you add custom and unique functionality that may not be available in the public registry.