BrowseFull catalogOutcomesSolve a specific problemRolesStack by teamTrustFilter by risk tier
← Back to Claude Tool Reviews

MetaMCP

Connector Setup & Config Solid

MCP aggregator that combines multiple MCP servers into a unified endpoint with namespace management, tool selection, and OAuth. Single Docker container.

2,202 starsMIT (commercial OK)FreeDeveloper setup

2.2K stars. Solves 'too many MCP servers' — consolidates all tool connections into one managed proxy.

Power users with 5+ MCP servers who want a single unified endpoint instead of managing each separately.

Claude Code Claude Cowork Claude Chat

https://github.com/metatool-ai/metamcp

By metatool-ai

How to Get It

Option 1: Claude Desktop AppOpen the Customize panel in the sidebar → browse connectors → search and add. Works in Claude Code, Claude Cowork, and Claude Chat.
CostFree

Trust Signals Reviewed

Stars2,202Contributors20Last updated2026-02-08LicenseMIT (OK for commercial use)Known CVEsNone foundSources: GitHub Advisory Database + OSV.dev · Scanned 2026-04-11 · scanner v1

Data & Access

Data processingPrompts sent to Anthropic API. Enterprise/Team plans exclude training.

Community Pulse Active

Discussed on Hacker News, Reddit

28 mentions across 2 sources

Reviewer notes

Reviewed review. These are observations, not a security certification.

Scored from trust signals (evidence-eval-v1): 2,202 GitHub stars; 20 contributors; last commit 101d ago; license MIT.

2026-05-10: Useful when you're running 5+ MCP servers and the per-connection config overhead is becoming a real maintenance problem—MetaMCP collapses them into a single endpoint with namespaced tooling and OAuth in one Docker container. The tradeoff is real: you're introducing a proxy layer that becomes a single point of failure, and any downstream MCP instability now surfaces through a shared chokepoint. OAuth config per backend still requires upfront work, so don't expect zero setup. Pairs well with stable, well-maintained MCP servers; less suited to experimental or unreliable ones.

How to evaluate tools before deploying →

Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.

Evaluation

Ease of Use
4/5
Versatility
5/5
Reliability
5/5
Security
3/5
Overall score4.35 / 5.00 SolidEvaluatedMay 2026
Scored from trust signals (evidence-eval-v1): 2,202 GitHub stars; 20 contributors; last commit 101d ago; license MIT.

← Back to Claude Tool Reviews

Rolling Claude out in your org? Let's talk.

Start a conversation →