Skip to main content
Glama

Related Servers

Alternatives to Tunnel Manager

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for managing SSH connections to remote servers, providing host registry, session pool, and secure command execution with read-only protection.
      24 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server providing safe, persistent SSH sessions to remote machines with multi-hop ProxyJump tunneling, SFTP file transfer, and stored host profiles.
      524 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for SSH remote execution, file transfer, and file editing with automatic backup/trash and ~/.ssh/config integration.
      117 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for managing a remote host via FTP/FTPS/SFTP/SSH, offering file transfer, optional shell execution, and MySQL query tools.
      191 npm
      1
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      A server that enables secure interaction with remote SSH hosts through standardized MCP interface, providing functions like listing hosts, executing commands, and transferring files using native SSH tools.
      7
      558 npm
      105
      MIT

    TDQS

    C2.3/5.0

    Scored across 41 tools

    Disambiguation3/5

    The remote vs. inventory families mirror each other almost one-for-one (run_command, send_file, receive_file, copy_ssh_config, rotate_key), so an agent must read the description to know whether it wants single-host or bulk. Host management is also split across tunnel_manager_add_host/get_host/list_hosts/remove_host, tunnel_manager_load_inventory/save_inventory, and tunnel_ingest_hosts, which blur into each other. The namespace prefixes and terse descriptions help somewhat, but boundaries remain fuzzy.

    Naming Consistency3/5

    Most tools follow tm_<domain>_<verb>_<noun> (tm_remote_run_command, tm_file_content_search), which is readable and consistent. However, host CRUD uses a completely different tunnel_manager_* prefix, there is an orphan tunnel_ingest_hosts, and the descriptions for the tunnel_manager_* tools are generic 'Invoke the X operation' stubs. Two parallel naming schemes for overlapping concerns drag this down.

    Tool Count2/5

    41 tools is well past the point where a set stays scannable, and much of the bulk comes from duplicated single-host/bulk-inventory pairs. The domain is broad (SSH, inventory, files, security, system intel) but several tools feel like namespace filler rather than distinct capabilities.

    Completeness3/5

    Coverage is broad — connection checks, key rotation, file transfer, inventory sync, operation lifecycle, security auditing, and system discovery are all present. But there are notable gaps: no update/edit_host despite add/get/list/remove, no session close or per-operation result retrieval beyond progress/metrics, and no key or credential management surface. Agents would hit dead ends on common edit-style workflows.

    Maintenance

    ActivityActive
    ResponsivenessLimited data