MCP Directory

How to add Pipedream MCP to Cursor

One hosted MCP server for 2,800+ apps and 10,000+ tools, with Pipedream Connect managing OAuth for your users. Paste the config into ~/.cursor/mcp.json and restart Cursor.

Last updated June 14, 2026 · 12k★ · http · oauth · official

Cursor config for Pipedream MCP

npx @pipedream/mcp
{
  "mcpServers": {
    "pipedream-mcp": {
      "url": "https://remote.mcp.pipedream.net/v3",
      "type": "streamable-http",
      "headers": {
        "Authorization": "Bearer <your-pipedream-access-token>",
        "x-pd-project-id": "<your-project-id>",
        "x-pd-environment": "development",
        "x-pd-external-user-id": "<your-users-id>",
        "x-pd-app-slug": "<app-slug-e.g.-slack>"
      }
    }
  }
}

Remote server — no local install needed. Restart the client after saving the config.

Setup steps

  1. 1Open Cursor → Settings → MCP → Add new MCP server (or edit ~/.cursor/mcp.json directly).
  2. 2Paste the Pipedream MCP config below into the "mcpServers" object.
  3. 3Fill in placeholder secrets, then save.
  4. 4Cursor reloads MCP servers automatically — check Settings → MCP for a green status dot.
  5. 5Ask Cursor to use one of Pipedream MCP's tools to confirm it's connected.

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 + Cursor FAQ

Where is the Cursor config file?

Cursor reads MCP servers from ~/.cursor/mcp.json. Paste the Pipedream MCP config there under the "mcpServers" key and restart the client.

Is Pipedream MCP safe to use with Cursor?

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.

View repo Full Pipedream MCP page