Skip to main content
Glama
KamorionLabs

MCP Environment Proxy

by KamorionLabs

Related Servers

Alternatives to MCP Environment Proxy

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP auth wrapper and credential broker for multi-account workflows, enabling profile switching, secret injection, and policy enforcement for upstream MCP servers.
      348 npm
      4
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      A local, transparent MCP proxy with an admin console that connects MCP clients to downstream MCP servers, forwards requests unchanged, and exposes live operational events over a localhost dashboard.
      8 npm
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      A self-hosted MCP control plane and protocol gateway that aggregates and manages multiple MCP servers, exposing them via stable, authenticated MCP endpoints for any client.
      0
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Self-hosted MCP proxy and aggregation platform. Register multiple upstream MCP servers and expose them through a single unified endpoint with namespace routing, multi-transport support (HTTP/SSE, stdio, OpenAPI→MCP), per-tool overrides, and a web admin UI.
      18
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Local-first CLI + proxy that curates your MCP servers per client from one canonical config, cutting tool-schema tokens ~80% and resolving secret references instead of hardcoding keys.
      -
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for AWS SSO authentication and profile management, enabling AI assistants to check identity, switch profiles, and manage EC2/EKS resources.
      8
      MIT

    TDQS

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a distinct and clear purpose: getting current context, listing contexts, listing proxied tools, calling a proxied tool, and switching contexts. There is no overlap.

    Naming Consistency5/5

    All tool names use a consistent verb_noun pattern in snake_case (e.g., get_current_context, list_contexts), with clear and predictable naming.

    Tool Count5/5

    Five tools is appropriate for a proxy server that manages contexts and proxies tool calls; each tool serves a necessary role without redundancy.

    Completeness5/5

    The tool set covers the full lifecycle: switching contexts, viewing context info, listing available tools, and executing proxied calls. There are no obvious gaps for the stated domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues