Skip to main content
Glama
mcollina

PermShell MCP

by mcollina
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to PermShell MCP

No user-submitted related servers found.

    Related Servers

    • 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

    • 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
      23 npm
      2
      -

    • 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

    • Simple Subprocess MCP Server

      yonaka15
      F
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables LLM applications to safely execute shell commands with error handling and timeout settings.
      1
      -

    • 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
      6,170 npm
      740
      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.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: execute-command runs arbitrary shell commands, while system-info retrieves system information. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool based on the task.

    Naming Consistency4/5

    Both tools use a consistent hyphenated naming style (execute-command and system-info), which is readable and predictable. However, the pattern is not a standard verb_noun convention, and with only two tools, it's hard to assess full consistency, but there are no deviations in the limited set.

    Tool Count3/5

    With only 2 tools, the server feels thin for a shell-related purpose, as it might lack operations like file management, process control, or environment handling. While the tools cover basic execution and info, the count is borderline low for a typical shell utility scope.

    Completeness2/5

    For a shell server, there are significant gaps: no tools for file operations (e.g., list, read, write), process management, network commands, or environment variables. The surface is severely incomplete, as agents cannot perform common shell tasks beyond command execution and system info retrieval.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources