Shell MCP Server
Related Servers
Alternatives to Shell MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that allows LLMs to execute shell commands and receive their output in a controlled manner.7MIT
- FlicenseBqualityDmaintenanceA Model Context Protocol server that enables LLM applications to safely execute shell commands with error handling and timeout settings.1-
- FlicenseNot gradedqualityDmaintenanceA secure interface that enables language models to execute shell commands on the host operating system through the Model Context Protocol.1-
- AlicenseAqualityDmaintenanceA Model Context Protocol server for secure local system operations, enabling shell command execution and file management via a standardized interface.141Apache 2.0
- FlicenseAqualityDmaintenanceA local Model Context Protocol server that allows LLMs to securely execute shell commands on remote Linux and Windows systems via SSH connections.63 npm2-
- AlicenseNot gradedqualityDmaintenanceProvides secure, sandboxed terminal access for AI assistants via the Model Context Protocol, with multi-layer risk analysis and auditable command execution.7 npm8MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'run_command' has a clear and distinct purpose that cannot be confused with any other tool in this set.
The naming is perfectly consistent as there is only one tool. It follows a clear verb_noun pattern ('run_command'), and with no other tools to compare against, there is no inconsistency in naming conventions.
A single tool is too few for a server named 'Shell MCP Server', which implies broader shell-related functionality. This minimal set feels thin and under-scoped, as it only covers basic command execution without supporting common shell operations like listing files, checking processes, or managing environment variables.
The tool set is severely incomplete for a shell server. While 'run_command' covers arbitrary command execution, it lacks tools for specific shell tasks (e.g., file operations, process management, directory navigation), leaving significant gaps that will likely cause agent failures when trying to perform common shell workflows.