Pipeworx vs Smithery
live data gateway vs MCP server directory
one unified MCP gateway with ~290 live data sources behind it.
discovering and hosting third-party MCP servers from a directory.
Smithery is an MCP directory and hosting platform that indexes third-party MCP servers and offers hosted deployment for some of them. Pipeworx is a single MCP gateway running ~290 first-party data packs behind one URL. The choice is structural: do you want to pick servers from a marketplace and wire each one separately, or do you want one gateway URL that gives an agent access to a curated, monitored, primary-source data catalog?
Side-by-side
| Pipeworx | Smithery | |
|---|---|---|
| Model | Single MCP gateway, first-party packs | Directory + hosting of third-party MCP servers |
| Data coverage | ~290 packs, ~1,000 tools — all curated | Hundreds of indexed third-party servers — quality varies |
| Reliability | Telemetry-driven; 6.9% error rate on calls | Depends on each server's author |
| Auth & rate limiting | Unified across all packs (anon/BYO/account) | Varies per server |
| Compound / meta tools | Yes — ask_pipeworx, discover_tools, entity_profile, etc. | No (servers are independent) |
| Resource URIs for citations | Yes — pipeworx://… | Per server |
| Single connection setup | One URL → ~290 sources | One config block per server |
When to use which
Use Smithery if
- You want to browse the third-party MCP ecosystem and pick specific servers
- You need a single specialized server with no overlap with Pipeworx
- You're looking for hosting for an MCP server you've built
Use Pipeworx if
- You want one URL that covers live data without picking servers individually
- You need consistent auth, rate limiting, telemetry, and reliability across sources
- You want gateway-native meta-tools that cut round-trips by 5–15×
- You're building agents that need durable, citable output
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 Smithery?
Pipeworx is hosted on its own infrastructure rather than through Smithery's hosted offering. The Pipeworx gateway is available at https://gateway.pipeworx.io/mcp and works with any MCP-compatible client.
Should I use a directory or a gateway?
Different shapes for different needs. A directory like Smithery is useful when you want to pick one specialized server. A gateway like Pipeworx is useful when you want broad, curated, monitored access to many sources behind one connection — the cost of researching, installing, and maintaining ~290 separate MCP servers would be enormous.