Skip to main content
Glama
mcpgate
by ishaan1732

Related Servers

Alternatives to mcpgate

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      Not graded
      quality
      A
      maintenance
      Aggregates multiple backend MCP resource servers (Stdio, SSE, and Streamable HTTP) into a single unified endpoint exposed over SSE, Streamable HTTP, or Stdio. Enables routing of tool calls, resource access, and per-tool enable/disable or rename overrides through an optional web admin UI with configurable API key or bearer-token authentication.
      104 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides a security and context-control layer that multiplexes multiple MCP servers behind a single endpoint, scanning tool definitions and results, enforcing authorization, rate limiting, and audit logging, and dynamically retrieving tools to manage context window usage.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Fronts many downstream MCP servers through one session, presenting a unified tool namespace with collision resolution, fleet-wide allow/deny/hide policy, per-tool rate limits, centralized audit logging, Prometheus metrics, and bearer-key auth at the edge. Supports both stdio drop-in and Streamable HTTP deployment so agents point at a single endpoint instead of N servers.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Presents one governed MCP endpoint in front of many tool domains, routing every call through a single executor that enforces per-tool RBAC, rate limits, schema validation, encrypted secrets and PII-masked, hash-chained audit logging. It also lets teams register, validate and four-eyes approve new HTTP-backed tools at runtime so they appear to clients without a restart.
      MIT