Skip to main content
Glama
deepsuthar496

Remote Command MCP Server

by deepsuthar496
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Remote Command MCP Server

No user-submitted related servers found.

    Related Servers

    • stela-mcp

      Sachin-Bhat
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server for secure local system operations, enabling shell command execution and file management via a standardized interface.
      14
      1
      Apache 2.0

    • SSH MCP Server

      vilasone455
      F
      license
      A
      quality
      D
      maintenance
      A local Model Context Protocol server that allows LLMs to securely execute shell commands on remote Linux and Windows systems via SSH connections.
      6
      3 npm
      2
      -

    • SSH MCP Server

      tufantunc
      A
      license
      A
      quality
      A
      maintenance
      A Model Context Protocol server that allows LLMs to securely execute shell commands on remote Linux and Windows systems via SSH. It supports password and key-based authentication, command timeouts, and sudo elevation for administrative tasks.
      14
      7,741 npm
      747
      MIT

    • SSH MCP Server

      mfangtao
      A
      license
      B
      quality
      D
      maintenance
      A server that enables remote command execution over SSH through the Model Context Protocol (MCP), supporting both password and private key authentication.
      1
      1 npm
      2
      MIT

    • Shell MCP Server

      odysseus0
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that allows LLMs to execute shell commands and receive their output in a controlled manner.
      7
      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

    B3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or confusion between tools. The tool's purpose is singular and clearly defined.

    Naming Consistency5/5

    Since there is only one tool, it inherently maintains consistency. The naming follows a clear verb_noun pattern (execute_remote_command).

    Tool Count2/5

    A single tool is too few for a server named 'Remote Command MCP Server', which suggests a broader scope for remote command execution. This minimal set limits functionality and may cause agent failures due to lack of supporting operations.

    Completeness1/5

    The tool surface is severely incomplete. It only provides command execution with no support for listing available commands, checking command status, handling outputs, or managing remote sessions, which are essential for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources