What is the key difference between Pluggedin MCP Proxy and Metatool App?

Pluggedin MCP Proxy 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 Pluggedin MCP Proxy 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 Pluggedin MCP Proxy and Metatool App free or paid?

Pluggedin MCP Proxy operates under a Free / Open Source model (OAuth 2.0). Metatool App operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

Pluggedin MCP Proxy lists 6 tools with 1 views and 135 GitHub stars. Metatool App lists 6 tools with 2 views and 2,653 GitHub stars.

Can I use both Pluggedin MCP Proxy 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

Pluggedin MCP Proxy vs Metatool App

In-depth architectural comparison of the Pluggedin MCP Proxy 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

Pluggedin MCP Proxy

Aggregators · Local stdio

Quality: 53/100 (Good) | Auth: OAuth 2.0

Metatool App

Aggregators · Local stdio

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

Verdict Summary: Choose Pluggedin MCP Proxy 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 Pluggedin MCP Proxy when:

You need dedicated capabilities in the Aggregators domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
Primary tools included: Supports STDIO, SSE, and Streamable HTTP MCP servers, Runs as STDIO or Streamable HTTP, Aggregates tools, prompts, resources, and resource templates.

Explore Pluggedin MCP Proxy 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.
Primary tools included: .

Feature & Specification Comparison

Specification	Pluggedin MCP Proxy VeriTeknik Aggregators	Metatool App metatool-ai Aggregators
Summary	A comprehensive proxy server that combines multiple MCP servers into a single interface with extensive visibility features. It provides discovery and management of tools, prompts, resources, and templates across servers, plus a playground for debugging when building MCP servers.	MetaMCP is the one unified middleware MCP server that manages your MCP connections with GUI.
Category & Scope

Tools & Capabilities Breakdown

Pluggedin MCP Proxy Tools (6)

Supports STDIO, SSE, and Streamable HTTP MCP servers

Runs as STDIO or Streamable HTTP

Aggregates tools, prompts, resources, and resource templates

Provides document search with semantic relevance and filters

Tracks document attribution, versions, visibility, and deduplication

Supports workspaces, notifications, and OAuth token management

Metatool App Tools (6)

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).

Pluggedin MCP Proxy Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "veriteknik-pluggedin-mcp-proxy": {
      "command": "npx",
      "args": [
        "-y",
        "@pluggedin/pluggedin-mcp-proxy@latest"
      ]
    }
  }
}

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

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

More alternatives to Pluggedin MCP Proxy More alternatives to Metatool App Aggregators category hub Canonical compare URL