Skip to main content
Glama
VanSchulist

mcp-mesh

by VanSchulist
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-mesh

No user-submitted related servers found.

    Related Servers

    • mcp-search-proxy

      p1s4
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables clients of tool-heavy MCP aggregators to find and use upstream tools on demand through four fixed bridge tools (search, describe, call, refresh), cutting per-turn tool context from ~180k tokens to ~2–3k. It merges multiple upstream servers behind sticky sessions and a local lexical BM25 index, so only the schemas actually needed are retrieved.
      8
      MIT
    • fastmcp-gateway by Ultrathink-Solutions

      fastmcp-gatewayofficial

      Ultrathink-Solutions
      A
      license
      Not graded
      quality
      A
      maintenance
      Aggregates tools from multiple upstream MCP servers and exposes them through 4 meta-tools, enabling LLMs to discover and use hundreds of tools without loading all schemas upfront.
      149 PyPI
      3
      Apache 2.0

    • MCP Gateway

      MikkoParkkola
      F
      license
      A
      quality
      A
      maintenance
      A multiplexing gateway that aggregates multiple MCP servers into a single port, significantly reducing context token usage through a Meta-MCP discovery system. It enables dynamic tool discovery and invocation across various transport protocols including stdio, HTTP, and SSE.
      15
      78
      -

    • MCP Coordinator

      CyberClash
      A
      license
      Not graded
      quality
      D
      maintenance
      Acts as a proxy for multiple MCP servers, reducing context window usage from 15,000+ tokens to ~500 tokens by dynamically loading servers on-demand and exposing only 3 tools instead of all tool definitions.
      5
      GPL 3.0

    • MCP Nexus

      Aidan-Kay
      A
      license
      Not graded
      quality
      B
      maintenance
      A single MCP endpoint for AI agents to browse, inspect, and call tools from multiple upstream MCP servers without loading all schemas upfront, reducing context overhead.
      7 npm
      ISC
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct phase of the gateway workflow: search, describe, invoke, and status. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    All names use the 'mesh_' prefix and snake_case, but 'mesh_status' is a noun while the others follow a verb_noun pattern. This is a minor deviation that remains predictable and readable.

    Tool Count5/5

    Four tools are well-scoped for a gateway that aggregates many downstream servers. Each tool serves a clear, non-redundant purpose, and the count is neither too thin nor excessive.

    Completeness4/5

    The core gateway lifecycle is covered: discovery via search, inspection via describe, execution via invoke, and monitoring via status. A minor gap exists in not providing a direct 'list all servers/tools' operation without keywords, but agents can work around this.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources