Skip to main content
Glama
zachlikefolio

tunnel-mcp

by zachlikefolio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to tunnel-mcp

No user-submitted related servers found.

    Related Servers

    • claude-agent-bus

      Imolatte
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code agents on the same project to message each other directly, with server-side guardrails, human oversight and control via Telegram, approval workflows for outside changes, and one-tap sharing of agent setup.
      MIT

    • pairwave

      goofypluto999
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables two Claude Code sessions to connect over an end-to-end encrypted channel for collaborative AI-assisted development, with MCP tools for messaging, code sharing, and turn-taking.
      -

    • interclaude

      alexgoodell
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables peer-to-peer communication between Claude Code sessions, allowing them to send messages, hand off tasks, and coordinate across worktrees without manual intervention.
      MIT
    • crosstalk by epode-studio

      crosstalkofficial

      epode-studio
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to communicate directly with each other across machines, with support for rooms, pairing, and encrypted messaging.
      5 npm
      8
      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

    A3.8/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a distinct role: open/join/close for session lifecycle, invite for member management, say/share/receive for communication, listen for polling, and status for inspection. No overlapping functionality.

    Naming Consistency5/5

    All tools follow a consistent 'tunnel_verb' pattern, with clear action verbs like open, join, close, invite, say, share, receive, listen, status.

    Tool Count5/5

    9 tools cover the full scope of a collaborative tunnel session without being excessive. Each tool serves a necessary function.

    Completeness5/5

    The tool surface covers creation, joining, leaving, inviting, messaging, file sharing, artifact retrieval, event listening, and session status. No obvious missing operations for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources