Manifold vs OpenWork MCP Gateway
A side-by-side look at the Manifold 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 Manifold for aggregators work over a hosted endpoint; choose OpenWork MCP Gateway for aggregators over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Manifold when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
NetworkPolicy, headers.bypass, true.
Choose OpenWork MCP Gateway when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a remote HTTP/SSE transport.
- 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 | 52/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 24,232 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Manifold | View OpenWork MCP Gateway |
Tools & capabilities
Manifold tools 3
NetworkPolicyheaders.bypasstrue
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.
Manifold
{
"mcpServers": {
"manifold": {
"url": "https://mcp.notion.com/mcp"
}
}
}
OpenWork MCP Gateway
{
"mcpServers": {
"openwork-mcp-gateway": {
"url": "https://api.openworklabs.com/mcp/agent"
}
}
}
Frequently asked questions
Manifold is categorized under Aggregators and uses a remote HTTP/SSE transport. OpenWork MCP Gateway belongs to Aggregators and uses a remote HTTP/SSE transport. Pick Manifold 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.
Manifold has no declared pricing — check the project's own site. 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 manifold and openwork-mcp-gateway as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Manifold has a quality signal of 52/100 (Good) with 2 views, 0 installs and 4 GitHub stars. OpenWork MCP Gateway has 49/100 (Fair) with 1 views, 0 installs and 24,232 GitHub stars.