Skip to main content
Glama
meomeo-dev

shell-as-mcp

by meomeo-dev

Related Servers

Alternatives to shell-as-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables execution of arbitrary CLI tools and shell scripts by defining them in YAML configuration files as MCP Tools. Supports custom shells (bash, Python, Node.js, Deno), input parameters passed as environment variables, and flexible timeout settings.
      12 npm
      36
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Dynamically exposes CLI/bash commands as MCP tools and creates structured AI prompt templates through simple YAML configuration files, enabling users to transform any command-line tool into an MCP-compatible interface without writing code.
      20
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Turns any shell command into an MCP server by defining command-line tools in simple YAML files. Enables AI agents to execute system commands, security scanners, DevOps tools, and CLI utilities directly from chat interfaces.
      4
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables users to define and run MCP tools using declarative YAML configs with built-in trust enforcement, credential brokering, and tamper-evident audit logging.
      14
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Wraps any CLI tool and exposes its subcommands as MCP tools with typed parameters, supporting both config-driven mode for structured commands and fallback mode for raw CLI execution.
      -

    TDQS

    B3.4/5.0

    Scored across 49 tools

    Disambiguation2/5

    Multiple healthz tools across bundles (ffmpeg__healthz, ass__healthz, shell__healthz, etc.) are functionally identical, and several ffmpeg transcode tools (export_video, generate_proxy, process_video_for_llm) have overlapping parameters and purposes. The ytdlp summary/full pairs add further ambiguity.

    Naming Consistency4/5

    Tool names consistently follow a bundle__verb_noun pattern with snake_case, and the bundle prefix provides a clear namespace. Minor deviations exist (e.g., ffmpeg__extract_frames_for_vision vs. simple verb_noun names), but the overall pattern is predictable.

    Tool Count2/5

    49 tools is excessive for a coherent server; it aggregates multiple independent domains (ffmpeg, yt-dlp, ASS, safe command, host info) into one namespace. The high count is inflated by redundant healthz checks and trivial wrappers, making selection and navigation burdensome.

    Completeness3/5

    Major subdomains like ffmpeg and yt-dlp have decent coverage, but the shell bundle is nearly empty (only a trivial echo script), and there are notable gaps such as no simple audio extraction tool and no unified status/diagnostics tool. The broad scope makes full completeness difficult to assess.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues