A side-by-side look at the One and Sealgate 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 Sealgate for aggregators as a local process. You can also run both side by side in one mcpServers block.
ONE_SECRET, ONE_IDENTITY, ONE_IDENTITY_TYPE, ONE_PERMISSIONS, ONE_CONNECTION_KEYS, ONE_ACTION_IDS, ONE_KNOWLEDGE_AGENT.list_one_integrations, find_one_actions, execute_one_action.SEALGATE_GATEWAY_URL, SEALGATE_API_KEY.list_mcp_servers, get_session_status.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 57/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | ONE_SECRETONE_IDENTITYONE_IDENTITY_TYPEONE_PERMISSIONSONE_CONNECTION_KEYSONE_ACTION_IDSONE_KNOWLEDGE_AGENT | SEALGATE_GATEWAY_URLSEALGATE_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 11 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 3 | 2 |
| Full listing | View One | View Sealgate |
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 platformlist_mcp_serversList the MCP servers governed by your Sealgate gateway, with access-control classification and connection status.get_session_statusReview recent agent sessions and audit events: what agents did, which data flowed, and any blocked actions.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.
{
"mcpServers": {
"one": {
"command": "npx",
"args": [
"-y",
"@withone/mcp"
],
"env": {
"ONE_SECRET": "YOUR_ONE_SECRET_HERE",
"ONE_IDENTITY": "YOUR_ONE_IDENTITY_HERE",
"ONE_IDENTITY_TYPE": "YOUR_ONE_IDENTITY_TYPE_HERE",
"ONE_PERMISSIONS": "YOUR_ONE_PERMISSIONS_HERE",
"ONE_CONNECTION_KEYS": "YOUR_ONE_CONNECTION_KEYS_HERE",
"ONE_ACTION_IDS": "YOUR_ONE_ACTION_IDS_HERE",
"ONE_KNOWLEDGE_AGENT": "YOUR_ONE_KNOWLEDGE_AGENT_HERE"
}
}
}
}
{
"mcpServers": {
"sealgate": {
"command": "npx",
"args": [
"-y",
"@sealgate/mcp"
],
"env": {
"SEALGATE_GATEWAY_URL": "YOUR_SEALGATE_GATEWAY_URL_HERE",
"SEALGATE_API_KEY": "YOUR_SEALGATE_API_KEY_HERE"
}
}
}
}