Skip to main content
Glama
mustafaTokmak

container-mcp

by mustafaTokmak
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to container-mcp

No user-submitted related servers found.

    Related Servers

    • sandbox-mcp

      bird
      A
      license
      A
      quality
      D
      maintenance
      Provides a local, isolated Linux VM sandbox for AI agents using Apple's Virtualization.framework, enabling fast command execution (~60ms) and package management without cloud costs.
      35
      1
      MIT

    • agentpc

      pawanpaudel93
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to create, drive, checkpoint, reset and delete resettable Windows and Ubuntu desktop VMs on Apple Silicon Macs, giving them real desktops to click, type and screenshot in plus shell commands, file transfer and port forwarding. All processing is local, so agents can work in isolated guests without leaving the Mac.
      2
      MIT

    • WSL Manager

      bostrot
      F
      license
      Not graded
      quality
      A
      maintenance
      Lets AI agents manage local virtual machines: create macOS and Linux VMs on Apple silicon and WSL distros on Windows, start/stop, clone, back up, and run commands inside them.
      4,025
      -

    • autobox

      freakynit
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to run JavaScript in fresh V8 isolates and shell commands under macOS seatbelt sandboxing, with per-call permissions for network, CPU, memory, disk, and host mounts. It also supports persistent writable copies with explicit sync or discard for safe host directory edits.
      120 npm
      3
      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.8/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct operation—containers vs images, lifecycle vs inspection vs logs—with no overlapping functionality. An agent can easily select the correct tool.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, e.g., list_containers, run_container, pull_image. Minor variations like container_logs are still clear and predictable.

    Tool Count5/5

    With 15 tools, the set is well-scoped for container management—covering containers, images, and system status without being overwhelming or sparse.

    Completeness4/5

    Covers essential container and image lifecycle operations (CRUD, logs, stats, exec, copy, pull, build, prune). Missing operations like commit or rename are tertiary; the surface is highly functional.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources