Skip to main content
Glama
Sign In
Gatsuke

The Context-Saver

by Gatsuke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to The Context-Saver

No user-submitted related servers found.

    Related Servers

    • MCP Gateway

      neondeveloperz
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients to connect through a single multiplexed SSE/HTTP endpoint to multiple local and remote MCP servers, with token authentication, per-tool approval policies, tool namespacing, and live telemetry.
      38 npm
      1
      MIT

    • mcp-orchestrator

      rupinder2
      A
      license
      A
      quality
      F
      maintenance
      Enables connecting multiple downstream MCP servers into a single gateway, with unified tool search, namespacing, and deferred loading to preserve context window.
      2
      6
      MIT

    • 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
      85
      -
    • jev-router by ini8labs

      jev-routerofficial

      ini8labs
      A
      license
      A
      quality
      C
      maintenance
      Enables agents to connect through a single gateway that has a decision model pick which MCP tools and playbooks are relevant to each request, so the LLM only sees the few schemas it needs, and to then invoke those tools on the underlying servers. This cuts tool-selection cost and prompt size dramatically when many MCP servers are connected.
      2
      4
      MIT

    • mcpgate

      SlateGitOrg
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes any number of upstream MCP servers (stdio subprocesses or Streamable HTTP endpoints) as one MCP server for LLM agents, with namespaced tool names so servers cannot shadow each other. Every tool call passes centralized OAuth 2.1 bearer validation, per-client tool RBAC, rate limits, JSON Schema argument checks, a hash-chained audit log, and tool-definition pinning that quarantines changed tools until an operator approves them.
      MIT
    • AISIX AI Gateway by api7

      AISIX AI Gatewayofficial

      api7
      A
      license
      A
      quality
      A
      maintenance
      Self-hosted MCP gateway that registers upstream MCP servers and fronts them behind one governed Streamable HTTP endpoint: per-tool access control by caller API key, guardrails over tool arguments and results, rate limits, and usage logs. The same Rust gateway also proxies LLM and A2A agent traffic.
      1
      206
      Apache 2.0
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4.1/5.0

    Scored across 8 tools

    Disambiguation4/5

    The tools are mostly distinct: discovery is split into list_tools (compact list), search_tools (keyword search), suggest_tools (prompt-ranked with schemas), and get_tool_schema (single schema load), with clear boundaries. The main overlap is list_servers vs gateway_status, both of which expose upstream health/circuit-breaker state, though the descriptions differentiate cheap orientation from detailed status reporting.

    Naming Consistency4/5

    All names use snake_case and most follow a predictable verb_object pattern: list_servers, list_tools, search_tools, suggest_tools, get_tool_schema, call_tool, reload_config. gateway_status is the one noun-phrase outlier, a minor deviation rather than a pattern break.

    Tool Count5/5

    Eight tools is well-scoped for a gateway that needs to orient, discover, load schemas, invoke upstream tools, report health, and reload config. Each tool has a clear role in the workflow, and there is no obvious padding.

    Completeness4/5

    The surface covers the core gateway lifecycle: list servers/tools, search and suggest tools, fetch schemas, call upstream tools, report status, and reload configuration. Minor gaps remain around explicit server connection management, circuit-breaker reset, or MCP resources/prompts if those upstream capabilities are in scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources