Skip to main content
Glama
jakenuts

mcp-cli-exec MCP Server

by jakenuts

Related Servers

Alternatives to mcp-cli-exec MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      D
      maintenance
      Enables safe execution of system shell commands with real-time streaming output and rich metadata capture. Provides configurable command execution with timeout controls, environment management, and extensible plugin architecture for monitoring command lifecycles.
      4
      -
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables the execution of arbitrary bash commands and returns detailed output including stdout, stderr, and exit codes. It supports customizable working directories, execution timeouts, and environment variable configurations.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables executing arbitrary shell commands over Streamable HTTP, with configurable shell, working directory, environment, timeout, and output limits, returning stdout, stderr, exit code, and termination details.
      25 npm
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      An MCP server that enables users to execute arbitrary shell commands on their local machine and receive the output. It provides a terminal tool for running system commands through MCP-compatible clients using the Python SDK.
      1
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A cross-platform shell command execution server that supports Windows, macOS, and Linux environments with PowerShell, CMD, GitBash, and Bash shells, optimized for Japanese language environments.
      82 npm
      MIT
    • 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

    TDQS

    C2.9/5.0

    Scored across 2 tools

    Disambiguation2/5

    The two tools have significant overlap in purpose, both executing CLI commands. While cli-exec-raw specifies 'raw' and 'structured output', the distinction is subtle and could easily lead to confusion about which to use for basic command execution. The descriptions don't clearly delineate when to choose one over the other.

    Naming Consistency4/5

    Both tools follow a consistent cli-exec prefix pattern with hyphenated suffixes. The naming is predictable and readable, though the suffix conventions differ slightly (one has no suffix, the other uses '-raw'). This minor deviation keeps it from a perfect score.

    Tool Count3/5

    With only 2 tools, the server feels thin for a CLI execution domain. While it covers basic execution, more operations like command validation, history tracking, or batch processing might be expected. The count is borderline minimal but functional for core tasks.

    Completeness2/5

    For a CLI execution server, there are notable gaps. Missing tools for command chaining, environment variable management, output parsing beyond 'structured', or error handling make the surface incomplete. Agents will hit dead ends when needing advanced CLI interactions beyond simple execution.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues