Pipeworx vs Glama

live data gateway vs MCP marketplace

Pipeworx is for

one MCP gateway with ~290 first-party live data sources.

Glama is for

browsing third-party MCP servers and tools through a curated catalog.

Glama is an MCP marketplace and hosting platform that catalogues third-party MCP servers with quality scoring. Pipeworx is a single MCP gateway running ~290 first-party data packs behind one URL — designed for autonomous-agent traffic that needs broad live-data coverage without picking and wiring individual servers.

Side-by-side

	Pipeworx	Glama
Model	Single gateway, first-party packs	Marketplace + hosting for third-party servers
Coverage	~290 packs of live data	Hundreds of third-party servers across categories
Quality control	First-party — telemetry, error rates measured	Quality scoring on third-party submissions
Setup	One URL → ~290 sources	One config per server
Meta-tools	Yes — collapse 5–15 calls into one	No
Citable URIs	Yes — pipeworx://…	Per server

When to use which

Use Glama if

You want to browse third-party MCP servers with quality ratings
You need specialized servers outside the live-data category
You're looking for hosting for an MCP server you've built

Visit Glama →

Use Pipeworx if

You want one URL covering ~290 live data sources
You need consistent telemetry, auth, and reliability across all calls
You want gateway-native meta-tools that fan out across packs

Get started — free

Connect Pipeworx in one line

Add this to your MCP client (Claude Desktop, Cursor, VS Code, Claude Code, etc.) — no API keys required for public data sources.

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Common questions

Is Pipeworx listed on Glama?

Pipeworx is hosted on its own infrastructure at https://gateway.pipeworx.io/mcp. Glama focuses on third-party MCP server hosting rather than gateways.

Why not just pick servers from Glama instead of using Pipeworx?

If you need one specific server, that's a reasonable choice. If you need broad live-data coverage, picking and wiring 20+ third-party servers individually means 20+ auth schemes, 20+ failure modes, and 20+ rate-limit policies. Pipeworx unifies that behind one URL with measured reliability.