Shell is a global group of energy and petrochemical companies, one of the oil and gas supermajors, operating in more than 70 countries with businesses including oil and gas exploration and production, refining, and marketing.
Why this server?
Provides enhanced command execution in shell environments with improved error handling and security controls
Why this server?
Provides protection against shell injection and secure command execution with safety features
Why this server?
Provides the ability to execute shell scripts (bash/sh) with safety measures and restrictions
Why this server?
Allows execution of whitelisted shell commands with comprehensive security features including command and flag whitelisting, path validation, and protection against injection attacks.
Why this server?
Implements tools for executing shell commands with security restrictions
Why this server?
Provides ability to run BASH/SH shell scripts and view results
Why this server?
Allows executing shell commands within a Docker container, providing a secure and isolated environment for running commands.
Why this server?
Provides a bridge for AI agents to safely execute shell commands in various shells (bash, zsh, fish, powershell, cmd), with support for both single-line and multi-line commands, detailed error handling, and system information retrieval.
Why this server?
Enables controlled execution of shell commands across PowerShell, CMD, and Git Bash with security restrictions, command blocking, and history tracking.
Why this server?
Enables execution of common shell commands like ls, cat, pwd, grep, wc, touch, and find.
Why this server?
Provides secure execution of shell commands with protective measures against dangerous operations including file system destruction, permission changes, and privilege escalation.
Why this server?
Enables running shell commands with structured output, including support for single commands, chained commands, or arrays of commands in specified working directories. Returns detailed execution results with stdout, stderr, exit codes, and execution duration.
Why this server?
Enables execution of shell commands within projects, allowing for running tests, linting, and other command-line operations
Why this server?
Provides the ability to execute shell commands safely using a list of arguments, giving access to system information and utilities.
Why this server?
Enables execution of shell commands through tagged server capabilities
Why this server?
Provides audit capabilities to track and monitor shell access to pods.
Why this server?
Includes Shell execution capabilities, enabling the MCP to run shell commands on the host system programmatically.
Why this server?
Includes shell execution capabilities, allowing the MCP to run shell commands on the host system
Why this server?
Supports installation and execution through shell commands, with environment variable configuration for different search providers and APIs.
Why this server?
Allows execution of shell commands in a controlled environment
Why this server?
Enables execution of shell commands across multiple platforms (Windows, macOS, Linux) with platform-specific command whitelists and security levels.
Why this server?
Nash MCP provides capabilities to execute shell commands with error handling and output capture
Why this server?
Used for executing commands and configuring environment variables for remote connections.
Why this server?
Provides a secure interface to execute shell commands on the host system with features such as command output capture, working directory specification, command timeouts, and enhanced security controls.
Why this server?
Provides cross-platform shell command execution with automatic platform-specific shell selection between cmd.exe and /bin/sh
Why this server?
Provides access to shell command history, enabling users to search, explore, and retrieve previously executed commands from Bash and other shell environments.
Why this server?
Provides tools for executing shell commands on connected Android devices, offering access to the underlying Android operating system for automation tasks.
Why this server?
Enables secure execution of shell commands in specified directories with support for multiple shell types, timeout control, and built-in security features to safely run system commands for file operations, git commands, package management, and system monitoring.
Why this server?
Enables execution of shell commands in a dedicated workspace directory, returning command output or error messages to the AI
Why this server?
Provides controlled access to ShellJS commands for filesystem operations, including read-only functions (ls, grep, find) and optional read-write capabilities (mkdir, touch, cp, mv, rm, sed).
Why this server?
Offers Shell script integration for installation, configuration and execution of the krep MCP server across different environments
Why this server?
Allows for executing shell commands as custom tools, with configuration options to enable or disable this capability for security reasons
Why this server?
Enables execution of shell commands on a VM through the MCP interface, allowing remote interaction with the VM's command line.
Why this server?
Reports on available shells, shell configurations, aliases, and functions.
Why this server?
Allows running shell commands and capturing their output through the shell_command function