Skip to main content
Glama
mlzoo

amazon-quick-exec-mcp

by mlzoo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to amazon-quick-exec-mcp

No user-submitted related servers found.

    Related Servers

    • host-shell-mcp

      funkyfunc
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to execute shell commands on a host macOS computer with configurable file access permissions, granting access to credentials and tools while enforcing sandbox restrictions.
      MIT

    • permission-aware-mcp

      TanvirIslam-BD
      F
      license
      A
      quality
      D
      maintenance
      Enables secure file system operations (read, write, delete) and simulated command execution with server-enforced permission policies, risk assessment, and human-in-the-loop approval.
      5
      -

    • Shell MCP Server

      heffrey78
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables safe shell command execution with configurable directory and command restrictions, allowing Claude Desktop to run shell commands securely.
      MIT

    • Terminal MCP Server

      dha-aa
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Desktop or other MCP clients to execute shell commands, read/write files, and list directories on the local machine. Includes basic safety guardrails to block obviously destructive operations.
      -

    • cli-mcp

      gabry848
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides secure execution of terminal commands (PowerShell, CMD, shell) with configurable security policies including command blocking, path restrictions, and timeout.
      1
      -
    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

    A4.1/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool owns a distinct slice of the shell workflow: shell_execute for synchronous commands vs shell_start for background jobs, and the job lifecycle tools (list/output/wait/kill) are clearly separated from each other and from shell_info. Descriptions explicitly cross-reference when to use which (e.g. timeout overflow -> shell_start), leaving no realistic misselection.

    Naming Consistency5/5

    Every tool uses snake_case with a consistent shell_ prefix, and the shell_job_* family groups the background-job operations predictably (start, list, output, wait, kill). No mixed conventions or vague verbs.

    Tool Count5/5

    Seven tools is well-scoped for a shell-execution server: one synchronous path, one background-job lifecycle, plus a configuration probe. No tool feels redundant or padding.

    Completeness4/5

    The surface covers synchronous execution, the full background lifecycle (start, snapshot output, block, list, kill), and environment introspection — a complete operational loop. The only minor gap is no way to write new stdin to an already-running job, which agents can work around by designing the initial command.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources