OpenWork MCP Gateway vs Treg.to
A side-by-side look at the OpenWork MCP Gateway and Treg.to MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose OpenWork MCP Gateway for aggregators work over a hosted endpoint; choose Treg.to for aggregators. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose OpenWork MCP Gateway when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 48/100 · Fair | 43/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 24,196 | 5,874 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View OpenWork MCP Gateway | View Treg.to |
Tools & capabilities
OpenWork MCP Gateway tools
No tool names declared yet. Check the project README from the listing page.
Treg.to 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": {
"openwork-mcp-gateway": {
"url": "https://api.openworklabs.com/mcp/agent"
}
}
}
Treg.to
No confirmed install command for Treg.to yet — follow the setup steps linked from its listing page rather than a guessed package name.