Skip to main content
Glama
797,950 tools. Updated 2026-11-17 23:17

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

  • 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
  • Search past agent sessions reconstructed from recorded shell commands by prompt, directory, executor, or date to identify which session did the work, then replay its timeline.
    MIT
  • Search recorded shell commands by text to find individual commands, exit codes, timestamps, and directories—useful for 'did I run X' or 'what broke here'.
    MIT
  • Run shell commands with enforcement of permission rules: read operations allowed, destructive commands blocked unless permitted.
    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.
    5
    -
  • A
    license
    Not graded
    quality
    D
    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.
    10 npm
    4
    Apache 2.0

Matching MCP Connectors

  • Execute arbitrary shell commands on a remote Kali Linux machine for advanced scenarios when dedicated tools do not cover the task.
    MIT
  • Rebuild the chronological timeline of an AI agent session from recorded shell commands, prompts, exit codes, and timestamps, page by page.
    MIT
  • Lists simulated files, HTTP endpoints, MCP servers and shell commands available to programs run by lugh_run, showing each allowed action before execution.
    MIT
  • Execute shell commands over SSH inside a running VM and capture combined stdout and stderr output.
    MIT
  • Intercepts risky shell commands before execution, blocking rm -rf, DROP, format, path traversal, and unconstrained deletes to prevent destructive agent actions.
    MIT
  • Run shell commands in a sandbox to safely execute AI-generated code and retrieve stdout, stderr, and exit code.
    Apache 2.0
  • Run shell commands directly from LLMs with explicit user permission via PermShell MCP. Specify command, directory, timeout, and input for secure execution.
    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
  • Run development commands in your workspace—builds, tests, git, and language toolchains. Executes allowlisted executables without a shell; destructive commands require confirmation.
    MIT
  • Review recent shell audit events to identify blocked or bypassed commands, then select the exact allow_pattern label needed for retrying a command that was incorrectly refused.
    -
  • Execute shell commands on remote servers via SSH with captured stdout, stderr, and exit codes for system administration and automation tasks.
    MIT
    Destructive
  • Execute shell commands on remote servers via SSH, capturing stdout/stderr/exit code, with automatic blocking of dangerous operations unless confirmed.
    MIT