Manifold vs Metatool App

A side-by-side look at the Manifold and Metatool App MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Manifold logoManifoldAggregators · Remote HTTP/SSEMCP gateway aggregating MCP servers and OpenAPI/Swagger REST APIs behind one MCP endpoint52GoodAuth: not declaredMetatool App logoMetatool AppAggregators · Local subprocess (stdio)MetaMCP is the one unified middleware MCP server that manages your MCP connections with GUI.45FairAuth: no auth required

Verdict: choose Manifold for aggregators work over a hosted endpoint; choose Metatool App for aggregators as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Manifold logoChoose 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.
Explore Manifold

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecManifold logoManifoldMetatool App logoMetatool App
CategoryAggregatorsAggregators
Quality signal52/100 · Good45/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars42,723
Directory activity 2 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
Tools3Not listed

Tools & capabilities

Manifold tools 3

  • NetworkPolicy
  • headers.bypass
  • true

Metatool App 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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "manifold": {
      "url": "https://mcp.notion.com/mcp"
    }
  }
}

Metatool App

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

Frequently asked questions

Manifold is categorized under Aggregators and uses a remote HTTP/SSE transport. Metatool App belongs to Aggregators and uses a local stdio subprocess. Pick Manifold for aggregators work and Metatool App 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. Metatool App is listed as free. Auth: no auth required. 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 metatool-ai-metatool-app 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. Metatool App has 45/100 (Fair) with 3 views, 0 installs and 2,723 GitHub stars.