How to add Pipedream MCP to Claude Desktop
One hosted MCP server for 2,800+ apps and 10,000+ tools, with Pipedream Connect managing OAuth for your users. Paste the config into ~/Library/Application Support/Claude/claude_desktop_config.json and restart Claude Desktop.
Last updated June 14, 2026 · 12k★ · http · oauth · official
Claude Desktop config for Pipedream MCP
npx @pipedream/mcp{
"mcpServers": {
"pipedream-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://remote.mcp.pipedream.net/v3",
"--header",
"Authorization: Bearer <your-pipedream-access-token>",
"--header",
"x-pd-project-id: <your-project-id>",
"--header",
"x-pd-environment: development",
"--header",
"x-pd-external-user-id: <your-users-id>",
"--header",
"x-pd-app-slug: <app-slug-e.g.-slack>"
]
}
}
}Claude Desktop connects to remote servers through the `mcp-remote` proxy (installed on first run via npx). Restart Claude Desktop after saving.
Setup steps
- 1Open Claude Desktop → Settings → Developer → Edit Config (this opens ~/Library/Application Support/Claude/claude_desktop_config.json).
- 2Paste the Pipedream MCP config below under the top-level "mcpServers" key.
- 3Fill in any placeholder secrets (API keys, paths) in the snippet.
- 4Save the file, then fully quit and reopen Claude Desktop.
- 5Open a chat and confirm Pipedream MCP's tools appear under the 🔌 tools menu.
Before you start
- A Pipedream account and project (connected user accounts are stored in the project)
- A Pipedream OAuth client — exchange client credentials for the access token sent as the Bearer token
- For self-hosting the reference server: Node.js/pnpm and PIPEDREAM_CLIENT_ID, PIPEDREAM_CLIENT_SECRET, PIPEDREAM_PROJECT_ID, PIPEDREAM_PROJECT_ENVIRONMENT env vars
Security
Your users' third-party OAuth grants and API keys are stored by Pipedream Connect, so you're delegating credential custody to Pipedream (their security docs detail how grants are handled); the Bearer access token and x-pd-project-id/x-pd-environment headers are secrets in their own right. The in-repo server is an unmaintained reference implementation — use the hosted remote server for production.
Pipedream MCP + Claude Desktop FAQ
Where is the Claude Desktop config file?
Claude Desktop reads MCP servers from ~/Library/Application Support/Claude/claude_desktop_config.json. Paste the Pipedream MCP config there under the "mcpServers" key and restart the client.
Is Pipedream MCP safe to use with Claude Desktop?
Your users' third-party OAuth grants and API keys are stored by Pipedream Connect, so you're delegating credential custody to Pipedream (their security docs detail how grants are handled); the Bearer access token and x-pd-project-id/x-pd-environment headers are secrets in their own right. The in-repo server is an unmaintained reference implementation — use the hosted remote server for production.
Is Pipedream MCP free, and is it safe to hand over credentials?
Developing in a project's development environment is free; production Connect usage is billed per Pipedream's pricing. On safety: the entire value proposition is that Pipedream Connect stores and brokers your users' OAuth grants and keys per its published security docs — that custody trade-off (convenience vs. a third party holding credentials) is the main decision to make.
What's the difference between mcp.pipedream.com and remote.mcp.pipedream.net?
mcp.pipedream.com is the consumer-facing site: log in, connect your own accounts, copy per-app server endpoints. remote.mcp.pipedream.net/v3 is the developer endpoint for embedding MCP in your product, driven by Bearer auth plus headers/params that identify your project, your end user (externalUserId), and the target app.
Can I self-host it?
There's a reference implementation in the monorepo's modelcontextprotocol/ directory (npx @pipedream/mcp, SSE and streamable-HTTP routes per user and app), but Pipedream marks it unmaintained and it still depends on the hosted Connect API for auth and execution. It demonstrates the architecture; it is not a standalone alternative.