What is the key difference between MCPDiscovery and Metatool App?

MCPDiscovery belongs to the Aggregators category with local stdio execution, while Metatool App belongs to the Aggregators category with local stdio execution.

How do I install MCPDiscovery or Metatool App in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are MCPDiscovery and Metatool App free or paid?

MCPDiscovery operates under a Free / Open Source model (No auth required). Metatool App operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

MCPDiscovery lists 5 tools with 2 views and 52 GitHub stars. Metatool App lists 6 tools with 2 views and 2,670 GitHub stars.

Can I use both MCPDiscovery and Metatool App together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

MCPDiscovery vs Metatool App

In-depth architectural comparison of the MCPDiscovery and Metatool App MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

MCPDiscovery

Aggregators · Local stdio

Quality: 40/100 (Fair) | Auth: No auth required

Metatool App

Aggregators · Local stdio

Quality: 47/100 (Fair) | Auth: API Key required

Verdict Summary: Choose MCPDiscovery if you need specialized Aggregators tools running via a local process. Choose Metatool App if your workspace requires Aggregators integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose MCPDiscovery when:

You need dedicated capabilities in the Aggregators domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Automatic discovery and configuration of MCP servers, Supports quick search for explicit requests, Supports deep search with planning, testing, and acting stages.

Explore MCPDiscovery Details

Choose Metatool App when:

You need dedicated capabilities in the Aggregators domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: METAMCP_API_KEY, METAMCP_OIDC_CLIENT_ID, METAMCP_OIDC_CLIENT_SECRET, METAMCP_OIDC_ISSUER, METAMCP_LOG_LEVEL.

Feature & Specification Comparison

Specification	MCPDiscovery particlefuture Aggregators	Metatool App metatool-ai Aggregators
Summary	MCP of MCPs. Automatic discovery and configure MCP servers on your local machine.	MetaMCP is the one unified middleware MCP server that manages your MCP connections with GUI.
Category & Scope	Aggregators

Tools & Capabilities Breakdown

MCPDiscovery Tools (5)

Automatic discovery and configuration of MCP servers

Supports quick search for explicit requests

Supports deep search with planning, testing, and acting stages

Multiple deployment options: remote, Docker, npx, source

Compatible with various MCP clients via config file entries

Metatool App Tools (6)

Dynamic aggregation of MCP servers into unified endpoints

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

MCPDiscovery Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "particlefuture-mcpdiscovery": {
      "command": "npx",
      "args": [
        "-y",
        "@1mcpserver/1mcpserver"
      ]
    }
  }
}

Metatool App Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "metatool-ai-metatool-app": {
      "command": "uvx",
      "args": [
        "mcp-hn"
      ],
      "env": {
        "METAMCP_API_KEY": "YOUR_METAMCP_API_KEY_HERE",
        "METAMCP_OIDC_CLIENT_ID": "YOUR_METAMCP_OIDC_CLIENT_ID_HERE",
        "METAMCP_OIDC_CLIENT_SECRET": "YOUR_METAMCP_OIDC_CLIENT_SECRET_HERE",
        "METAMCP_OIDC_ISSUER": "YOUR_METAMCP_OIDC_ISSUER_HERE",
        "METAMCP_LOG_LEVEL": "YOUR_METAMCP_LOG_LEVEL_HERE"
      }
    }
  }
}

Frequently Asked Questions

MCPDiscovery is categorized under Aggregators and uses a local stdio subprocess. In contrast, Metatool App belongs to Aggregators using local stdio subprocess. Select MCPDiscovery when you need capabilities focused on aggregators and Metatool App when you require tools for aggregators.

More alternatives to MCPDiscovery More alternatives to Metatool App Aggregators category hub Canonical compare URL