Skip to main content
Glama
459,394 tools. Updated 2026-08-17 07:11

"Bash shell scripting and command line resources" matching MCP tools:

  • Retrieve the full recorded output of a terminal command, including command line, exit code, and timing. Use a command id or negative offset to specify the command.
    MIT
  • 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 bash commands in a sandboxed environment. Use session IDs to maintain working directory, environment, and filesystem state across commands.
    Apache 2.0
  • Execute shell commands in a project directory with captured and truncated output, while Proofpane enforces governance and maintains a verifiable audit trail.
    MIT

Matching MCP Servers

  • A
    license
    A
    quality
    F
    maintenance
    Allows executing shell commands within a secure Docker container through Claude's MCP interface, providing Kubernetes tools and isolated environment without host Docker daemon access.
    2
    108
    5
    MIT

Matching MCP Connectors

  • Manage a Command+K workspace: widgets, conversations, MCP connections, and usage analytics.

  • 39-endpoint crypto trading intelligence MCP for AI agents. Streamable HTTP over x402 pay-per-use (Base USDC). Catalog tools + agent-strategy console.

  • 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
  • Execute shell commands on remote servers via SSH. Specify the server and command; optionally set timeout, working directory, or dry-run preview.
    Mozilla Public 2.0
  • Run the stored per-language build, lint, test, e2e, or verify command, optionally passing a single target argument, without ever executing arbitrary shell input.
    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
  • Run shell commands on a remote host in the background, get an instant job ID, and stream output line-by-line via ssh_tail. Ideal for builds, deploys, and log tails requiring real-time monitoring.
    MIT
  • Execute bash commands, manage background processes, and check status to handle builds, linting, and other CLI operations.
    Apache 2.0
  • 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
  • Execute a shell pipeline securely by validating each stage against an allowlist, using subprocess chaining to avoid shell injection and unsafe commands.
    MIT