Skip to main content
Glama
jahrulnr

mcp-docker-agentic

by jahrulnr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to mcp-docker-agentic

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.
      -
    • Smyth Docker Commander by SmythOS

      Smyth Docker Commanderofficial

      SmythOS
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables spawning ephemeral Linux sandbox containers using Docker and executing commands through an interactive TTY interface. Supports collaborative terminal sessions where both AI clients and humans can simultaneously interact with the same container.
      27
      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.9/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: file operations, exec, interactive sessions, background jobs, copying, and a no-op close. The most similar pair (docker_exec and docker_interactive_exec) is well-differentiated by TTY allocation and interactive input handling, so there is no real ambiguity.

    Naming Consistency5/5

    All tools consistently use snake_case with a docker_ prefix, and related tools share predictable sub-patterns (e.g., exec_result, exec_kill, interactive_*, cp_to/from). Minor style deviations like docker_mkdir and docker_grep are command-style but still readable and consistent with the overall naming convention.

    Tool Count4/5

    19 tools is slightly above the typical well-scoped range, but the count is justified by the broad domain of Docker interactions—file manipulation, execution, interactive sessions, background jobs, and copying. Each tool serves a distinct operational need, so the count feels appropriate rather than bloated.

    Completeness4/5

    The toolset comprehensively covers file operations, execution, background jobs, interactive sessions, and copying. However, it lacks container lifecycle management (e.g., listing, starting, stopping, inspecting containers), which would be expected for a broad Docker agentic server. This gap limits the toolset when discovering or managing containers rather than operating on a known one.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources