Comparison
metamcp vs awesome-mcp-servers
Verdict
Pick metamcp if metamcp is unique in its role as an MCP Aggregator, Orchestrator, Middleware, and Gateway encapsulated within one Docker container; pick awesome-mcp-servers if awesome-mcp-servers is a collection focused specifically on MCP servers with an emphasis on AI integration.
Markdown twin · metamcp alternatives · awesome-mcp-servers alternatives
GraphCanon updated 4w
Trust & integrity
| Signal | metamcp | awesome-mcp-servers |
|---|---|---|
| Maintenance | Steady (34d since push) As of 4w · github_public_v1 | Very active (6d since push) As of 1mo · github_public_v1 |
| Provenance | Not a fork · Organization account As of 4w · github_public_v1 | Not a fork · Personal account As of 1mo · github_public_v1 |
| OSV dependency advisories | No lockfile (source not queried) As of 1mo · osv@v1 | No lockfile (source not queried) As of 1mo · osv@v1 |
| deps.dev advisories | Not queried deps.dev@v1 | Not queried deps.dev@v1 |
| OpenSSF Scorecard | Not queried openssf-scorecard@v1 | Not queried openssf-scorecard@v1 |
Tagline
- metamcp
- MCP Aggregator, Orchestrator, Middleware, Gateway in one Docker container
- awesome-mcp-servers
- A collection of MCP servers
Stars
- metamcp
- 2.6k
- awesome-mcp-servers
- 91k
Forks
- metamcp
- 388
- awesome-mcp-servers
- 13k
Open issues
- metamcp
- 96
- awesome-mcp-servers
- 2.6k
Language
- metamcp
- TypeScript
- awesome-mcp-servers
- -
Adopt for
- metamcp
- Metamcp is unique in its role as an MCP Aggregator, Orchestrator, Middleware, and Gateway encapsulated within one Docker container.
- awesome-mcp-servers
- awesome-mcp-servers is a collection focused specifically on MCP servers with an emphasis on AI integration.
Persona
- metamcp
- -
- awesome-mcp-servers
- -
Runtime
- metamcp
- -
- awesome-mcp-servers
- -
License
- metamcp
- Metamcp is available under an MIT license.
- awesome-mcp-servers
- MIT
Last pushed
- metamcp
- Jun 22, 2026
- awesome-mcp-servers
- Jul 4, 2026
Categories
- metamcp
- Developer Tools
- awesome-mcp-servers
- Developer Tools
Trust and health
Maintenance
- metamcp
- Steady (60%)
- awesome-mcp-servers
- Very active (96%)
Days since push
- metamcp
- 34d
- awesome-mcp-servers
- 6d
Open issues (now)
- metamcp
- 96
- awesome-mcp-servers
- 2.6k
Owner type
- metamcp
- Organization
- awesome-mcp-servers
- User
Full report
- metamcp
- Trust report
- awesome-mcp-servers
- Trust report
Choose metamcp if…
- Requirements: Requires Docker; Requires a Docker environment to run.; Typically applicable in developer or deployment contexts that require handling MCP (Model Context Protocol)..
- Tags unique to metamcp: docker, gateway, middleware, orchestrator.
- metamcp ships Docker support for self-hosted deployment.
- - You need to aggregate multiple models under the Model Context Protocol and serve them through a unified interface within a dockerized environment
When NOT to use metamcp
- - If your application does not require all the services bundled into one Docker container, leading to potential resource wastage without utilizing the full feature set
- - In scenarios where specific customization of each component (aggregator, orchestrator, middleware, or gateway) is required and cannot be adequately addressed by a monolithic solution
Choose awesome-mcp-servers if…
- Tags unique to awesome-mcp-servers: ai, server-resources.
- If your project requires detailed resources and tools around MCP server capabilities for AI projects, awesome-mcp-servers is well-suited as it focuses solely on this niche area of technology.
- More GitHub stars (91k vs 2.6k) - visibility, not fit.
When NOT to use awesome-mcp-servers
- Avoid using awesome-mcp-servers if your project does not involve utilizing or exploring the specific functionalities of MCP servers in relation to AI applications.
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (metatool-ai/metamcp) · observed Jul 26, 2026
- GitHub forks (metatool-ai/metamcp) · observed Jul 26, 2026
- Last push (metatool-ai/metamcp) · observed Jun 22, 2026
- License file (MIT) · observed Jul 26, 2026
- Decision facts (enrichment) · observed Jul 17, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
- GitHub stars (punkpeye/awesome-mcp-servers) · observed Jul 26, 2026
- GitHub forks (punkpeye/awesome-mcp-servers) · observed Jul 26, 2026
- Last push (punkpeye/awesome-mcp-servers) · observed Jul 4, 2026
- License file (MIT) · observed Jul 26, 2026
- Decision facts (enrichment) · observed Jul 15, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
GitHub stars on cards: metamcp 2.6k · awesome-mcp-servers 91k (synced Jul 26, 2026).
Common questions
- What is the difference between metamcp and awesome-mcp-servers?
- metamcp: MCP Aggregator, Orchestrator, Middleware, Gateway in one Docker container. awesome-mcp-servers: A collection of MCP servers. See the comparison table for live GitHub stats and shared categories.
- When should I choose metamcp over awesome-mcp-servers?
- Choose metamcp over awesome-mcp-servers when Requirements: Requires Docker; Requires a Docker environment to run.; Typically applicable in developer or deployment contexts that require handling MCP (Model Context Protocol).; Tags unique to metamcp: docker, gateway, middleware, orchestrator; metamcp ships Docker support for self-hosted deployment; - You need to aggregate multiple models under the Model Context Protocol and serve them through a unified interface within a dockerized environment.
- When should I choose awesome-mcp-servers over metamcp?
- Choose awesome-mcp-servers over metamcp when Tags unique to awesome-mcp-servers: ai, server-resources; If your project requires detailed resources and tools around MCP server capabilities for AI projects, awesome-mcp-servers is well-suited as it focuses solely on this niche area of technology; More GitHub stars (91k vs 2.6k) - visibility, not fit.
- When should I avoid metamcp?
- - If your application does not require all the services bundled into one Docker container, leading to potential resource wastage without utilizing the full feature set - In scenarios where specific customization of each component (aggregator, orchestrator, middleware, or gateway) is required and cannot be adequately addressed by a monolithic solution
- When should I avoid awesome-mcp-servers?
- Avoid using awesome-mcp-servers if your project does not involve utilizing or exploring the specific functionalities of MCP servers in relation to AI applications.
- Is metamcp or awesome-mcp-servers more popular on GitHub?
- awesome-mcp-servers has more GitHub stars (90,602 vs 2,555). Stars measure visibility, not whether either tool fits your constraints.
- Are metamcp and awesome-mcp-servers open source?
- Yes - both are open-source projects on GitHub (metamcp: MIT, awesome-mcp-servers: MIT).
- Where can I find alternatives to metamcp or awesome-mcp-servers?
- GraphCanon lists graph-backed alternatives at metamcp alternatives and awesome-mcp-servers alternatives (metamcp markdown twin, awesome-mcp-servers markdown twin), ranked by typed relationship edges rather than popularity votes.
- Is there a machine-readable version of this comparison?
- Yes. The markdown twin at this comparison mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
- Which is better maintained, metamcp or awesome-mcp-servers?
- metamcp: Steady. awesome-mcp-servers: Very active. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.
- Where are the full trust reports for metamcp and awesome-mcp-servers?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: metamcp trust report; awesome-mcp-servers trust report.