The hard part of giving an agent access to thousands of SaaS tools isn't the tool definitions — it's the auth. Every app has its own OAuth dance, token refresh, and scope model, and you do not want those credentials flowing through an LLM's context. This directory is Pipedream's answer: a thin MCP layer in front of Connect, where the integration platform that already brokers credentials for 2,800+ APIs simply re-projects them as MCP tools.
What Sets It Apart
- Credentials stay server-side. The model receives tool schemas and results, never the OAuth tokens — Connect isolates and brokers them, and users can revoke access independently.
- The catalog is the moat: 2,800+ APIs and 10,000+ pre-built actions become callable tools without you wiring each integration by hand.
- Two addressing modes — per-app endpoints (
/{external_user_id}/{app}) or dynamic configuration — plus HTTP/Streamable, SSE, and stdio transports to fit different client runtimes.
Who It's For
Great fit if you're building a multi-tenant agent that needs to act in many users' SaaS accounts and want someone else to own the credential lifecycle. Look elsewhere if you only need one or two integrations — standing up Connect is overkill — or if you want a maintained codebase to fork: this reference implementation is no longer actively maintained, and Pipedream steers production users to its hosted remote MCP server instead.
