Skip to main content
Glama
joaoh82

rustunnel-mcp

by joaoh82
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Remote

Related Servers

Alternatives to rustunnel-mcp

No user-submitted related servers found.

    Related Servers

    • LivePort MCP

      dundas
      F
      license
      Not graded
      quality
      D
      maintenance
      Give AI agents access to your localhost dev server. Zero-config tunnel that works with Claude Code, OpenClaw, and any MCP-compatible agent. No interstitial pages, no account required.
      -

    • mcp-common-server

      tamilts124
      F
      license
      Not graded
      quality
      B
      maintenance
      Zero-dependency MCP server that provides AI models with secure read/write/exec access to local files and directories over HTTP and SSE, designed to be tunneled via ngrok for integration with Claude Web.
      -

    • mcp-connect

      myat-kyaw-thu
      A
      license
      Not graded
      quality
      B
      maintenance
      A dead simple MCP server for exposing your app functions to AI agents like Claude Desktop.
      7 npm
      6
      MIT

    • MCP Cloud Gateway

      unlimitedusers
      A
      license
      Not graded
      quality
      B
      maintenance
      Unifies local MCP servers into a single secure Cloudflare Tunnel endpoint, making them accessible to MCP clients like Notion and Claude. Supports HTTP/SSE/stdio servers, built-in file system tools, bearer authentication, and one-click Windows setup.
      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.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct concern: regions, active tunnels, tunnel history, creating/spawning a tunnel, obtaining manual connection info, and closing a tunnel. The related create_tunnel and get_connection_info are clearly separated by spawning behavior vs. returning CLI instructions.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: list_regions, list_tunnels, create_tunnel, close_tunnel, get_tunnel_history, get_connection_info. The naming style is uniform and predictable throughout.

    Tool Count5/5

    Six tools is well-scoped for a tunnel management server. Each tool covers a necessary part of the workflow without redundancy or bloat.

    Completeness5/5

    The tool surface covers the full tunnel lifecycle: create, list active, close, review history, discover regions, and obtain manual connection instructions. No obvious dead ends or missing critical operations for this domain.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources