OpenWork MCP Gateway vs Pipedream

A side-by-side look at the OpenWork MCP Gateway and Pipedream MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

OpenWork MCP Gateway logoOpenWork MCP GatewayAggregators · Remote HTTP/SSEYour OpenWork org's skills, plugins, workflows, and connections through one OAuth MCP URL.49FairAuth: oauth 2.0Pipedream logoPipedreamAggregatorsConnect with 2,500 APIs with 8,000+ prebuilt tools, and manage servers for your users, in your own app.45FairAuth: api key required

Verdict: choose OpenWork MCP Gateway for aggregators work over a hosted endpoint; choose Pipedream for aggregators. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

OpenWork MCP Gateway logoChoose OpenWork MCP Gateway when

  • You need dedicated capabilities in the Aggregators domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
Explore OpenWork MCP Gateway

Pipedream logoChoose Pipedream when

  • You need dedicated capabilities in the Aggregators domain.
  • Its auth model fits you: API key required.
Explore Pipedream

Feature & specification comparison

Rows where the two servers differ are marked.

SpecOpenWork MCP Gateway logoOpenWork MCP GatewayPipedream logoPipedream
CategoryAggregatorsAggregators
Quality signal49/100 · Fair45/100 · Fair
Install commandConfirmedNot confirmed yet
TransportRemote HTTP/SSE—
AuthOAuth 2.0API key required
PricingNot declaredFreemium
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars24,22811,758
Directory activity 1 views 0 installs 0 upvotes 7 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

OpenWork MCP Gateway tools

No tool names declared yet. Check the project README from the listing page.

Pipedream tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

OpenWork MCP Gateway

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "openwork-mcp-gateway": {
      "url": "https://api.openworklabs.com/mcp/agent"
    }
  }
}

Pipedream

No confirmed install command for Pipedream yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

OpenWork MCP Gateway is categorized under Aggregators and uses a remote HTTP/SSE transport. Pipedream belongs to Aggregators and uses an install path we have not confirmed yet. Pick OpenWork MCP Gateway for aggregators work and Pipedream for aggregators.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Pipedream has no confirmed install command yet — follow its own setup instructions.

OpenWork MCP Gateway has no declared pricing — check the project's own site. Auth: oauth 2.0. Pipedream is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add openwork-mcp-gateway and pipedreamhq-pipedream as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, OpenWork MCP Gateway has a quality signal of 49/100 (Fair) with 1 views, 0 installs and 24,228 GitHub stars. Pipedream has 45/100 (Fair) with 7 views, 0 installs and 11,758 GitHub stars.