Skip to main content
Glama
Swartdraak

Docker MCP Server

by Swartdraak
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Docker MCP Server

No user-submitted related servers found.

    Related Servers

    • Podman MCP Server

      manusa
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Podman and Docker container runtimes, enabling management of containers, images, networks, and volumes via AI assistants.
      83
      Apache 2.0

    • mcp-dockhand

      t1nk333r
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server exposing the Dockhand API as MCP tools. Enables AI assistants to manage Docker infrastructure including containers, stacks, images, networks, and volumes across multiple hosts.
      MIT

    • Docker-MCPilotS

      sopyk
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to manage Docker containers through a secure MCP interface, supporting container lifecycle operations, log inspection, resource monitoring, and system diagnostics with role-based access control.
      3
      MIT

    • DockerHub MCP Server

      keshavjha123
      A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready Model Context Protocol (MCP) server that provides comprehensive DockerHub integration for AI assistants. This server enables AI assistants to search, analyze, and manage Docker images through standardized MCP tools.
      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 12 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific Docker resources and actions. For example, create_container and run_container are well-differentiated by their descriptions, with run_container explicitly noted as the preferred method for starting containers. There is no ambiguity or overlap in functionality across the tool set.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, such as list_containers, create_container, and stop_container. This predictable naming convention makes it easy for agents to understand and select the appropriate tools without confusion.

    Tool Count5/5

    With 12 tools, the server is well-scoped for managing Docker containers, images, networks, and volumes. Each tool earns its place by covering essential operations like creation, listing, starting, stopping, and removal, without being overly sparse or bloated.

    Completeness4/5

    The tool set provides strong coverage for core Docker operations, including CRUD for containers and listing for other resources. Minor gaps exist, such as no tools for creating or removing networks/volumes, but agents can still perform most workflows effectively with the available tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources