Skip to main content
Glama
aihuali213

mcp-server-wslc

by aihuali213
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-server-wslc

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 & Kubernetes MCP Server

      TrivCodez
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to manage Docker containers and Kubernetes resources through natural language, supporting operations like container management, image building, and pod/deployment/service management.
      9
      MIT

    • ContainMind

      Ashfaqbs
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage and analyze containers across Docker and Podman through natural language, providing unified inspection, monitoring, and diagnostics.
      3
      -

    • oriel

      ParadoxInfinite
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to manage Docker containers, images, volumes, networks, and Compose projects through natural language, with secret masking and destructive action grants.
      3
      Apache 2.0
    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.6/5.0

    Scored across 28 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action pair, such as container_run vs container_create vs container_start, which are clearly differentiated by their descriptions. Resources like containers, images, volumes, networks, and registry operations are cleanly separated, leaving no ambiguity.

    Naming Consistency4/5

    Most tools follow the verb_noun pattern (e.g., container_create, image_pull, network_list), but a few like list_containers and list_images reverse the order, creating minor inconsistency. The overall structure is predictable and readable, with only slight deviations.

    Tool Count4/5

    With 28 tools, the count is on the higher end, but it corresponds to the broad domain of container management, covering containers, images, volumes, networks, and registry operations. Each tool serves a distinct purpose, making the size justified despite being above the typical 15-tool benchmark.

    Completeness4/5

    The tool surface provides comprehensive lifecycle coverage for containers (create, run, start, stop, restart, remove, inspect, logs, exec, stats), images (build, pull, push, tag, inspect, remove), and basic operations for volumes, networks, and registries. Minor gaps such as network connect/disconnect and volume inspect are present, but core workflows are well-supported.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources