Skip to main content
Glama
sneha4175

MCP Tool-Retrieval Gateway

by sneha4175
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to MCP Tool-Retrieval Gateway

No user-submitted related servers found.

    Related Servers

    • context-saver

      msuther898
      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

    • smartmcp

      spak2005
      A
      license
      Not graded
      quality
      C
      maintenance
      Intelligent MCP proxy server that reduces context bloat by serving only the tools your AI actually needs through semantic search and a fixed two-tool surface.
      12
      MIT

    • CtxSlim

      v01dst
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP proxy that reduces context bloat by exposing only relevant tools and compressing schemas, enabling efficient use of multiple MCP servers.
      2
      MIT

    • Tool Scout

      nabheet
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      MCP proxy server with semantic tool search for LLM coding agents. It reduces context window usage by activating only relevant tools based on user queries.
      -

    • mcp-compressor

      atlassian-labs
      A
      license
      Not graded
      quality
      A
      maintenance
      A proxy server that wraps existing MCP servers to significantly reduce token consumption by compressing tool descriptions into a two-step interface. It enables users to integrate extensive toolsets without exceeding context limits or incurring high API costs.
      118
      Apache 2.0

    • MCP Proxy Gateway

      steveweltman
      A
      license
      Not graded
      quality
      C
      maintenance
      A context-aware MCP proxy that reduces token usage by exposing only 3 tools (mcp_search, mcp_call, mcp_schema) to LLMs, with on-demand tool loading and BM25 search.
      65 npm
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are entirely distinct: find_tools is for discovery/searching across upstream servers, while call_tool is for execution. There is no functional overlap or ambiguity.

    Naming Consistency5/5

    Both tools follow the verb_noun pattern (find_tools, call_tool) with lowercase and underscores, making the naming predictable and consistent.

    Tool Count5/5

    As a gateway that dynamically exposes tools from many upstream servers, two meta-tools (discover and invoke) are exactly the right scope. Each tool earns its place, and adding more would be redundant.

    Completeness5/5

    The tool surface fully covers the domain of a retrieval/calling gateway: discover which tool to use (find_tools) and then invoke it (call_tool). There are no obvious missing operations for this purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources