One vs OpenWork MCP Gateway
A side-by-side look at the One and OpenWork MCP Gateway MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose One for aggregators work as a local process; choose OpenWork MCP Gateway for aggregators. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose One when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
ONE_SECRET. - You want tools like
list_one_integrations, find_one_actions, execute_one_action.
Choose OpenWork MCP Gateway when
- You need dedicated capabilities in the Aggregators domain.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 60/100 · Good | 44/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | OAuth 2.0 |
| Pricing | Not declared | Not declared |
| Required env vars | ONE_SECRET | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 11 | 24,235 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View One | View OpenWork MCP Gateway |
Tools & capabilities
One tools 3
list_one_integrationsList available platforms and active connections, each with the `access` it confers (full, methods, or specific actions)find_one_actionsFind the action for every operation a task needs, across platforms, with its documentation, in one call; `load` fetches more of a document or an alternative'sexecute_one_actionExecute an API action on a connected platform
OpenWork MCP Gateway 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.
One
{
"mcpServers": {
"one": {
"command": "npx",
"args": [
"-y",
"@withone/mcp"
],
"env": {
"ONE_SECRET": "YOUR_ONE_SECRET_HERE"
}
}
}
}
OpenWork MCP Gateway
No confirmed install command for OpenWork MCP Gateway yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
One is categorized under Aggregators and uses a local stdio subprocess. OpenWork MCP Gateway belongs to Aggregators and uses an install path we have not confirmed yet. Pick One for aggregators work and OpenWork MCP Gateway 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. OpenWork MCP Gateway has no confirmed install command yet — follow its own setup instructions.
One has no declared pricing — check the project's own site. Auth: api key required. OpenWork MCP Gateway has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 one and openwork-mcp-gateway as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, One has a quality signal of 60/100 (Good) with 0 views, 0 installs and 11 GitHub stars. OpenWork MCP Gateway has 44/100 (Fair) with 2 views, 0 installs and 24,235 GitHub stars.