Skip to main content
Glama
kaznak

Shell Command MCP Server

by kaznak
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Shell Command MCP Server

No user-submitted related servers found.

    Related Servers

    • K8s MCP Server

      saifeezibrahim
      A
      license
      Not graded
      quality
      D
      maintenance
      A Docker-based MCP server that enables Claude to run Kubernetes CLI tools (kubectl, istioctl, helm, argocd) in a secure containerized environment for managing and troubleshooting clusters.
      MIT

    • Terminal MCP Server

      AcosX
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables executing shell commands on the host system via an MCP tool, with JWT/OAuth authentication and audit logging for secure remote access.
      MIT

    • warden

      dsvxmedia
      A
      license
      Not graded
      quality
      C
      maintenance
      A sandboxed MCP server that executes shell commands inside ephemeral, locked-down Docker containers with no network by default, dropped capabilities, and an audit log, enabling secure agent-driven command execution.
      3
      MIT

    • Docker MCP Server

      zaycruz
      A
      license
      Not graded
      quality
      B
      maintenance
      Facilitates isolated code execution within Docker containers, enabling secure multi-language script execution and integration with language models like Claude via the Model Context Protocol.
      5
      MIT

    • tiny-agent-sandbox

      wesleyzhangwq
      A
      license
      A
      quality
      C
      maintenance
      Run Python, JavaScript, or shell snippets in secure, resource-limited Docker containers with no network access, exposed as MCP tools.
      2
      Apache 2.0
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are perfectly distinct: one for asynchronous execution and one for synchronous execution. Their names and descriptions clearly differentiate their purposes, with no overlap or ambiguity in functionality.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern with kebab-case (execute-bash-script-async and execute-bash-script-sync). The naming is predictable and uniform across the set.

    Tool Count2/5

    With only 2 tools, the server feels thin for a shell command domain. While it covers basic execution modes, it lacks tools for other common operations like file manipulation, process monitoring, or environment inspection, making the scope incomplete.

    Completeness2/5

    The toolset is severely incomplete for a shell command server. It only provides script execution in two modes, missing essential operations like listing files, checking system status, managing processes, or handling input/output redirection, which are core to shell interactions.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources