Skip to main content
Glama
davidkim9

Container Exec MCP Server

by davidkim9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Container Exec MCP Server

No user-submitted related servers found.

    Related Servers

    • gnosis-docker-mcp

      kordless
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Docker containers and images, including starting, stopping, listing, and building operations.
      2
      -

    • Docker MCP Server

      alisaitteke
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Docker containers, images, networks, volumes, and Compose services through the Model Context Protocol. It supports system operations, command execution within containers, and integration with Docker Hub and GitHub Container Registry.
      79 npm
      2
      MIT

    • Docker MCP Server

      ArkTechNWA
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to interact with Docker containers through safe, permission-controlled access to inspect, manage, and diagnose containers, images, and compose services with built-in timeouts and AI-powered analysis.
      -

    • Docker MCP Server

      marcelofmatos
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants like Claude to manage Docker containers, images, and Docker Compose deployments through the Model Context Protocol. Provides secure container lifecycle management, image operations, and multi-host Docker server connections.
      168 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: exec for command execution, get_container_info for detailed container metadata, and list_containers for container enumeration. There is no overlap in functionality, making tool selection straightforward for an agent.

    Naming Consistency4/5

    Two tools follow a consistent verb_noun pattern (get_container_info, list_containers), but exec uses a standalone verb without a noun. While the naming is readable and mostly consistent, the deviation from the pattern slightly reduces predictability.

    Tool Count4/5

    Three tools are reasonable for a Docker container management server, covering core operations like listing, inspecting, and executing commands. However, the scope feels slightly thin, as common operations like starting/stopping containers or managing images are missing, though not critically so.

    Completeness3/5

    The toolset covers basic read and execute operations (list, get, exec) but lacks lifecycle management tools such as start, stop, create, or delete containers. This creates notable gaps that agents may need to work around, limiting full container management workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources