Skip to main content
Glama

Related Servers

Alternatives to MCPNexus

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP proxy that reduces context usage through semantic tool routing, enabling on-demand discovery and routing of relevant tools.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that reduces token usage by lazily loading skills and tools only when needed, and routing repetitive subtasks to ML backends instead of the LLM.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A meta-server that aggregates multiple MCP servers into a single interface, reducing token usage by 98%+ through progressive tool discovery and direct code execution that processes data between tools without consuming context window space.
      16 npm
      10
      Apache 2.0
    • 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.
      19 npm
      ISC
    • A
      license
      A
      quality
      C
      maintenance
      A smart MCP proxy server that lazily loads relevant MCP tool servers based on project context, keeping AI tool counts within recommended limits. It enables agents to dynamically activate, deactivate, and discover MCP servers to optimize context usage.
      13
      3
      MIT

    TDQS

    A4.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: listing all servers, searching for servers, connecting to a server, and retrieving a tool schema. No overlaps.

    Naming Consistency4/5

    All tools start with 'mcpd_' and use snake_case, but the verb patterns vary: some have noun suffixes (get_schema) while others are bare verbs (find, list, connect). Mostly consistent.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its role as a registry/hub. Each tool earns its place, covering discovery, connection, and schema retrieval.

    Completeness4/5

    The tools cover the core workflow of discovering and connecting to servers. A minor gap is the lack of a disconnect or management tool, but the description indicates that after connect, MCP Nexus is no longer involved.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing