Skip to main content
Glama
bbt567

remote-ssh-mcp

by bbt567
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to remote-ssh-mcp

No user-submitted related servers found.

    Related Servers

    • ssh-mcp

      m-kvn
      A
      license
      A
      quality
      C
      maintenance
      Enables reading, writing, editing, searching, running commands, transferring files, and using git on a remote Linux server over SSH via MCP tools.
      22
      3
      AGPL 3.0

    • mcp-ssh-tool

      skot
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol (MCP) SSH client server that provides autonomous SSH operations for GitHub Copilot and VS Code. Enable natural language SSH automation without manual prompts or GUI interactions.
      20
      2
      MIT

    • MCP SSH Server

      liliangshan
      F
      license
      A
      quality
      C
      maintenance
      Enables remote command execution and SFTP file upload or download from any MCP client without a local SSH client, SCP, or PuTTY installed. Supports password or private key authentication with SHA256 host fingerprint verification, timeouts, output limits, and multiple configured server instances.
      5
      -

    • local-bridge

      tianshu-ai
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects local tools (browser, shell) to a remote MCP server via reverse-MCP, enabling the server agent to control your local browser and execute shell commands.
      840 npm
      Apache 2.0

    • TermSSH MCP

      rayss868
      A
      license
      Not graded
      quality
      C
      maintenance
      Terminal-first SSH access for MCP clients and AI agents, enabling interactive remote sessions, file uploads, and stateful workflows.
      5 npm
      1
      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.9/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct action (check, diagnose, exec, list, read, write, forward, stop, URI). The read/write tools are clearly split by text vs binary, and check vs local_diagnostics separate remote vs local concerns.

    Naming Consistency4/5

    Tools follow a consistent remote_ssh_ prefix, but the action part mixes verbs (exec, list, read, write, start, stop) with noun phrases (local_diagnostics, uri). This is a minor inconsistency in an otherwise readable pattern.

    Tool Count5/5

    12 tools is well-scoped for an SSH remote server, covering connection, diagnostics, command execution, file operations, port forwarding, and URI generation without bloat.

    Completeness4/5

    Core remote SSH workflows are covered: connectivity, exec, file read/write (text and binary), directory listing, port forwarding management. Minor gaps like file delete/rename are absent but not critical for typical remote SSH usage.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources