Log inSubmit server

Metatool App vs OpenWork MCP Gateway

A side-by-side look at the Metatool App 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.

Metatool App logoMetatool AppAggregators · Local subprocess (stdio)MetaMCP is the one unified middleware MCP server that manages your MCP connections with GUI.45FairAuth: no auth requiredOpenWork MCP Gateway logoOpenWork MCP GatewayAggregators · Remote HTTP/SSEYour OpenWork org's skills, plugins, workflows, and connections through one OAuth MCP URL.48FairAuth: not declared

Verdict: choose Metatool App for aggregators work as a local process; 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?

Metatool App logoChoose Metatool App when

  • You need dedicated capabilities in the Aggregators domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Metatool App

OpenWork MCP Gateway logoChoose OpenWork MCP Gateway when

  • You need dedicated capabilities in the Aggregators domain.
  • You prefer a remote HTTP/SSE transport.
Explore OpenWork MCP Gateway

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMetatool App logoMetatool AppOpenWork MCP Gateway logoOpenWork MCP Gateway
CategoryAggregatorsAggregators
Quality signal45/100 · Fair48/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars2,71624,196
Directory activity 3 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed
Full listingView Metatool App View OpenWork MCP Gateway

Tools & capabilities

Metatool App tools

No tool names declared yet. Check the project README from the listing page.

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.

Metatool App

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "metatool-ai-metatool-app": {
      "command": "uvx",
      "args": [
        "mcp-hn"
      ]
    }
  }
}

OpenWork MCP Gateway

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "openwork-mcp-gateway": {
      "url": "https://api.openworklabs.com/mcp/agent"
    }
  }
}

Frequently asked questions

Metatool App is categorized under Aggregators and uses a local stdio subprocess. OpenWork MCP Gateway belongs to Aggregators and uses a remote HTTP/SSE transport. Pick Metatool App 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.

Metatool App is listed as free. Auth: no auth required. OpenWork MCP Gateway 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 metatool-ai-metatool-app and openwork-mcp-gateway as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Metatool App has a quality signal of 45/100 (Fair) with 3 views, 0 installs and 2,716 GitHub stars. OpenWork MCP Gateway has 48/100 (Fair) with 1 views, 0 installs and 24,196 GitHub stars.

Popular comparisons with Metatool App

Popular comparisons with OpenWork MCP Gateway