Skip to main content
Glama
339,162 tools. Last updated 2026-07-30 06:04

"How to execute local shell commands" matching MCP tools:

  • Execute shell commands with vault secrets injected as environment variables, never exposing secrets to the agent. Supports local and remote execution with automated secret injection and audit logging.
    AGPL 3.0
  • Execute shell commands in an isolated Debian Linux sandbox to run code safely without affecting the host system. Use stdin for data input and set timeouts for long operations.
    MIT
  • Execute shell commands over SSH inside a running VM and capture combined stdout and stderr output.
    MIT
  • Execute shell commands in Windows environments with configurable working directory, timeout, and output lines, while adhering to security restrictions and shell-specific settings.
    MIT
  • Execute shell commands on a remote SSH host and receive structured output with stdout, stderr, and exit code for stateless command runs.
    MIT

Matching MCP Servers

  • F
    license
    A
    quality
    D
    maintenance
    An MCP server for tracking and managing AI command usage history using a PostgreSQL database. It enables users to log, search, and view statistics for various AI-related commands and their execution contexts.
    Last updated
    5
  • A
    license
    -
    quality
    C
    maintenance
    An MCP server that lets you define and run custom shell commands via YAML templates, with built-in tools for flashing and serial communication in embedded development.
    Last updated
    14
    4
    Apache 2.0

Matching MCP Connectors

  • Intent execution engine for autonomous agent task routing

  • Let ChatGPT, Claude & Cursor use your Mac: email, calendar, iMessage, Teams, files. Local, free.

  • Execute shell commands on remote servers via SSH with captured stdout, stderr, and exit codes for system administration and automation tasks.
    MIT
  • Execute shell commands on remote servers via SSH, capturing stdout/stderr/exit code, with automatic blocking of dangerous operations unless confirmed.
    MIT
  • Execute shell commands across multiple items in batches, substituting $item in each command and streaming output to separate files for parallel batch processing.
    Apache 2.0
  • Re-parses shell history files to update the SQLite index, making recent commands searchable. Safe to run repeatedly.
    MIT
  • Run commands securely with timeouts and output limits, preventing shell injection and memory issues.
    GPL 3.0
  • Perform full-text search on indexed shell commands. Supports keyword and prefix queries, returning newest matches with timestamp, shell, cwd, and exit code.
    MIT
  • Execute shell commands (cat, echo, ls, pwd) in the current working directory or a specified one. Commands are limited to allowed flags and no shell operators.
    Apache 2.0
  • Execute shell commands with full system access. Use for git, npm, pip, and any command-line task.
    MIT
  • Retrieve the current tmux-mcp configuration to determine whether tmux is installed and whether to route shell commands through tmux for the remainder of the task.
    MIT
  • Scan shell commands for injection, unsafe operations, and threats before execution. Use this tool to verify safety before running any CLI command generated by an LLM or from user input.
    Apache 2.0
  • Executes shell commands in an isolated sandbox for file management and dependency installation, returning stdout, stderr, and exit code.
    MIT
  • Run shell commands on the host system, capturing stdout, stderr, exit code, and timeout status. Commands are subject to rate limits and safety blocks for destructive patterns.
    MIT
  • Execute shell commands with sudo on a remote host using an existing SSH session, with optional sudo password for elevated privileges.
    MIT
  • Read recent output from a remote SSH shell session to monitor long-running commands without sending new input.
    MIT