Skip to main content
Glama

Related Servers

Alternatives to jev-router

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Puts a single MCP endpoint in front of many downstream MCP servers, routing each prompt to the right server and tools so an agent sees a few relevant tools instead of every schema. Reads run automatically, writes require explicit user confirmation via elicitation, and consequential calls are blocked by a risk gate that logs every routing decision and call.
      3
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI harnesses to connect to a single MCP endpoint that routes to multiple downstream MCP servers, discovering and executing capabilities on demand while keeping tool schemas out of context.
      4
      70 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Aggregates multiple Model Context Protocol servers into a single gateway to provide unified search, description, and execution of tools. It reduces context limit issues by dynamically fetching specific tool schemas only when needed rather than loading all available tools at once.
      14 npm
      22
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      A universal gateway that aggregates multiple MCP servers into a single interface while providing advanced token optimization, result filtering, and automated summarization. It enables efficient management of large tool catalogs and reduces context usage by up to 95% for major AI clients.
      25 npm
      16
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A gateway that aggregates multiple MCP servers into a single endpoint, namespacing their tools and forwarding calls, so an agent connects to one MCP to access the entire stack.
      MIT

    TDQS

    A3.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    jev_route handles selection/decision while jev_call handles execution. The two tools have clearly distinct roles with no overlap, so agents cannot misselect.

    Naming Consistency5/5

    Both tools use the jev_ prefix and a concise verb (route, call) in snake_case. The pattern is consistent and predictable.

    Tool Count5/5

    Two tools are exactly what a router needs: one to decide and one to invoke. No bloat or missing operation, so the count is well scoped.

    Completeness5/5

    The router covers the full flow of selecting relevant tools/playbooks and then calling a chosen tool. No obvious lifecycle gaps for its orchestration purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues