Is MetaMCP — Aggregate Many MCP Servers as One free to use?

Yes. MetaMCP — Aggregate Many MCP Servers as One is freely available on TokRepo. Check the Source & Thanks section on the asset page for the specific open-source license.

How do I install MetaMCP — Aggregate Many MCP Servers as One?

Visit the asset page on TokRepo and click "Copy for agent" to get the installation instructions. Most assets can be installed with a single command.

MCP ConfigsMay 12, 2026·2 min read

MetaMCP — Aggregate Many MCP Servers as One

Name: MetaMCP — Aggregate Many MCP Servers as One
Author: MCP Hub

MetaMCP aggregates multiple MCP servers into namespaces and exposes a single endpoint with tool overrides, middleware, and an inspector for debugging.

MCP Hub · Community

Agent ready

This asset can be read and installed directly by agents

TokRepo exposes a universal CLI command, install contract, metadata JSON, adapter-aware plan, and raw content links so agents can judge fit, risk, and next actions.

Native · 94/100Policy: allow

Agent surface

Any MCP/CLI agent

Kind

Mcp

Install

Single

Trust

Trust: Established

Entrypoint

docker-compose.yml

Universal CLI install command

npx tokrepo install 603c608a-2628-45a0-b761-f219ddaca320

install contract metadata JSON adapter plan raw content

Intro

MetaMCP aggregates multiple MCP servers into namespaces and exposes a single endpoint with tool overrides, middleware, and an inspector for debugging.

Best for: teams building an MCP ‘hub’ with per-namespace policies, overrides, and debugging tools
Works with: Docker + docker compose, Postgres (bundled), MCP servers as upstreams
Setup time: 20–45 minutes

Practical Notes

Data point: the recommended path is Docker Compose + a bundled Postgres volume.
Quant: keep namespaces small (5–15 tools) so tool context stays usable for LLMs.

Pattern: enforce policy at the namespace boundary

When you combine many upstream servers, the namespace becomes your policy layer:

filter or hide tools,
normalize tool names/descriptions,
and add logging.

Pattern: create an “inspection loop”

Run your client against the MetaMCP endpoint, then use the inspector to replay calls with saved configs. This turns tool integration from guesswork into a debuggable loop.

FAQ

Q: Is MetaMCP a single binary? A: It’s designed to run via Docker Compose (recommended) with supporting services.

Q: Why do tool overrides matter? A: Small metadata tweaks can drastically improve tool selection quality.

Q: How do I avoid tool explosion? A: Use namespaces + filters to keep only the tools users actually need.

🙏

Source & Thanks

Source: https://github.com/metatool-ai/metamcp > License: MIT > GitHub stars: 2,315 · forks: 339

Discussion

No comments yet. Be the first to share your thoughts.

Related Assets

pi-mcp-adapter — One Proxy Tool for MCP (Pi)

pi-mcp-adapter lets Pi use MCP servers without loading hundreds of tool defs; verified 666★ and pushed 2026-05-13.

MCP Configs

MCP Hub

ToolHive Desktop — Run MCP Servers in Containers

ToolHive Desktop UI helps you discover and run MCP servers in containers, with client auto-configuration and optional telemetry you can disable.

MCP Configs

MCP Hub

1MCP — Unified MCP Runtime + CLI Mode

1MCP aggregates MCP servers behind `1mcp serve` and adds CLI mode for agent workflows; verified 433★ and ships `inspect -> run` flow.

MCP Configs

MCP Hub

MongoDB MCP Server — npx + Read-Only Safety by Default

MongoDB MCP Server exposes MongoDB queries and optional Atlas admin tools to MCP clients via npx or Docker, with a read-only mode that reduces risk.

MCP Configs

MCP Hub

◈Home 🔍Search 👤Me