OpenWork MCP Gateway vs Skgate
A side-by-side look at the OpenWork MCP Gateway and Skgate 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 Skgate 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.
Choose Skgate when
- You need dedicated capabilities in the Aggregators domain.
- You have the keys it needs:
PUBLIC_URL, OIDC_ISSUER, OIDC_CLIENT_ID, OIDC_CLIENT_SECRET.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 48/100 · Fair | 37/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 | PUBLIC_URLOIDC_ISSUEROIDC_CLIENT_IDOIDC_CLIENT_SECRET |
| Verified owner | Community listing | Community listing |
| GitHub stars | 24,196 | 13 |
| 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 Skgate |
Tools & capabilities
OpenWork MCP Gateway tools
No tool names declared yet. Check the project README from the listing page.
Skgate 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"
}
}
}
Skgate
No confirmed install command for Skgate 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. Skgate belongs to Aggregators and uses an install path we have not confirmed yet. Pick OpenWork MCP Gateway for aggregators work and Skgate 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. Skgate has no confirmed install command yet — follow its own setup instructions.
OpenWork MCP Gateway has no declared pricing — check the project's own site. Skgate has no declared pricing — check the project's own site. 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 skgate 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 48/100 (Fair) with 1 views, 0 installs and 24,196 GitHub stars. Skgate has 37/100 (Fair) with 0 views, 0 installs and 13 GitHub stars.