Skip to main content
Glama

Related Servers

Alternatives to Shell Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that exposes a tool to execute shell commands on the host machine, with customizable working directory and timeout.
      2
      -
    • 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
      -
    • 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
    • F
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol server for safely executing shell commands in specified directories with directory restrictions, timeout control, and detailed logging.
      1
      -
    • A
      license
      A
      quality
      A
      maintenance
      A secure shell command execution server implementing the Model Context Protocol (MCP). This server allows remote execution of whitelisted shell commands with support for stdin input.
      1
      202
      MIT
    • 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

    TDQS

    A3.5/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusing it with another. Its purpose—execute a shell command—is explicit and unambiguous.

    Naming Consistency4/5

    A single tool cannot exhibit inconsistency, and 'terminal' is clear and readable. It is a noun rather than a verb_noun action name, so it does not fully follow the ideal convention.

    Tool Count4/5

    A shell server naturally needs only one general-purpose execution tool, so the count is well-scoped rather than bloated. It is on the thin side, but additional tools would likely be redundant wrappers.

    Completeness4/5

    Because arbitrary shell commands can cover file operations, process control, and environment inspection, the surface is functionally broad. Minor gaps exist around streaming output, session persistence, and structured error handling, but these are workable via shell.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data