Skip to main content
Glama
Sign In
Shell Exec MCP

Shell Exec MCP

by domdomegg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Shell Exec MCP

No user-submitted related servers found.

    Related Servers

    • bash-mcp

      tsunamaru
      A
      license
      A
      quality
      C
      maintenance
      Enables executing Bash commands, pipelines, and scripts across Windows, macOS, and Linux via MCP, with support for multiple runtimes, timeouts, working directories, and stream capture.
      2
      -

    • Run Command MCP Server

      stilllovee
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides tools for executing shell commands both synchronously and asynchronously with real-time output streaming and process management capabilities. It enables users to start background tasks, monitor progress, and manage long-running processes via Stdio or HTTP transports.
      452 npm
      MIT

    • mcp2term

      FreddyE1982
      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
      -
    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

    A3.8/5.0

    Scored across 2 tools

    Disambiguation4/5

    The two tools have largely distinct purposes: execute runs commands while get_job_status polls background jobs. However, the execute description refers to 'get_status' while the actual tool is named 'get_job_status', which could cause an agent to call a non-existent tool.

    Naming Consistency3/5

    The set mixes a bare verb ('execute') with a verb_noun pattern ('get_job_status'), and the description further muddies this by referencing a third name ('get_status'). It is still readable but not a predictable pattern.

    Tool Count4/5

    Two tools is minimal but reasonably matched to the narrow shell-execution scope, since running a command and checking job status are the two essential operations. It sits just under the typical 3-15 range.

    Completeness3/5

    Running commands and polling background jobs are covered, but there is no way to kill or cancel a long-running job, nor to list active jobs. These are notable gaps for a process-execution server where runaway commands are a common failure mode.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources