Skip to main content
Glama
Sign In
mcp-shell-server

mcp-shell-server

by tumf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-shell-server

  • SAGE

    PsYcGoD
    A
    license
    A
    quality
    B
    maintenance
    Local-first MCP server and CLI wrapper for AI coding agents. SAGE routes shell commands through a tracked local runner, stores command history on the user’s machine, and returns compressed terminal output to reduce noisy context.
    16
    53 PyPI
    11
    MIT

Related Servers

  • Shell MCP Server

    odysseus0
    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

  • stela-mcp

    Sachin-Bhat
    A
    license
    A
    quality
    D
    maintenance
    A Model Context Protocol server for secure local system operations, enabling shell command execution and file management via a standardized interface.
    14
    1
    Apache 2.0

  • Shell-MCP

    kevinwatt
    A
    license
    B
    quality
    D
    maintenance
    A secure MCP server for executing whitelisted shell commands with resource and timeout controls, designed for integration with Claude and other MCP-compatible LLMs.
    20
    389 npm
    7
    MIT

  • Shell Server

    sergio-deras
    F
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server that enables users to execute arbitrary shell commands through a terminal tool. It supports custom working directories, configurable execution timeouts, and safe command parsing using shlex.
    -
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.2/5.0

Scored across 1 tool

Disambiguation5/5

There is only one tool, so there is no overlap or possibility of misselection. Its purpose—executing an allowlisted shell command—is clear from the name and description.

Naming Consistency5/5

The sole tool name, shell_execute, is readable and uses a consistent snake_case style. With only one tool there is no convention mixing to penalize.

Tool Count3/5

A single execution tool is enough for a focused shell server, but the surface feels thin: no separate tool for inspecting allowlists, limits, or configuration. It is borderline minimal rather than well-scoped.

Completeness4/5

The core operation—running an allowed command—is covered, including timeout and output constraints in the description. However, there are minor gaps such as no tool to list allowed commands or report execution policy details.

Maintenance

ActivityMaintained
ResponsivenessUsually handled

Resources