Skip to main content
Glama
650,501 tools. Updated 2026-10-13 23:36

"List of Servers Running as Docker Containers" matching MCP tools:

  • List running Docker containers on a remote Linux machine. Include stopped containers with the all parameter.
    MIT
  • List running Docker containers to monitor active processes. Optionally show all containers, including stopped ones.
    MIT
  • List Docker containers running on a Synology NAS by providing the device ID. Monitor active containers to manage Docker deployments.
    -
  • List Docker containers on the daemon, showing running ones by default. Use all=True to include stopped containers, with optional filters, limit, and sparse detail.
    MIT

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables querying normalized real-world asset data through MCP tools, including listing assets, retrieving asset details, comparing yields against SOFR, and checking eligibility by jurisdiction.
    MIT

Matching MCP Connectors

  • List containers in a Docker Compose project with status, health, and ports. Filter by service or include stopped containers to inspect project state.
    MIT
  • List Docker volumes with driver, mountpoint, and the containers mounting them. Read-only; filter by glob pattern.
    Apache 2.0
  • List Docker networks with filters by name, ID, driver, or label. Optionally fetch extended details including connected containers for each network.
    MIT
  • List Docker containers via the local Engine API without the CLI; filter by state or name, include stopped ones, and return text or JSON.
    Apache 2.0
  • List Docker images with tags, IDs, sizes, and creation times via the local Engine API; filter by glob and return JSON or text without pulling, building, or removing.
    Apache 2.0
  • Reclaim disk space by deleting one kind of unused Docker object per call: stopped containers, dangling images, anonymous volumes, unused networks, or build-cache.
    Apache 2.0
    Destructive
  • Close pooled Docker client connections to discard stale or errored ones; they rebuild lazily on next use. Does not affect running containers.
    MIT
  • Get live CPU, memory, network I/O, and PID stats for running Docker containers. Pass container names/IDs or 'all' to monitor resource usage.
    MIT
  • List all Docker containers and images, including stopped ones, via a read-only Docker API call. Use it to get a quick Docker inventory on your Linux system.
    MIT
  • Retrieves a combined Docker snapshot covering containers, images, running stats, disk usage, and networks. Read-only via the Docker API; partial failures are reported in an errors field.
    MIT
  • Remove stopped Docker containers to reclaim disk space without affecting running ones. Optionally filter by age or label to narrow which stopped containers get pruned.
    MIT
    Destructive
  • Start, stop, restart, kill, pause, unpause, or remove a Docker container by name or ID to control its lifecycle.
    Apache 2.0
    Destructive
  • List Docker networks with driver, scope, subnet, gateway, and attached containers. Filter by name pattern or driver; output as text, JSON, YAML, or table.
    Apache 2.0
  • Inspect a single Docker network to retrieve its connected containers, IPAM config, and driver options for troubleshooting or configuration review.
    MIT
  • Identify what consumes Docker disk space with a breakdown by containers, images, volumes, and build cache. Uses read-only Docker API to diagnose storage usage.
    MIT