Skip to main content
Glama
hlavrencic

portainer-mcp-server

by hlavrencic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to portainer-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 MCP Server

      hypnosis
      A
      license
      A
      quality
      A
      maintenance
      Universal Docker MCP server for AI assistants (Cursor, Claude Desktop). Manage Docker containers, execute commands, query databases, and handle environment configurations — all through natural language.
      10
      225 npm
      MIT

    • mcp-portainer-lite

      Cuti27
      A
      license
      Not graded
      quality
      C
      maintenance
      Lightweight MCP server for Portainer CE, focused on Docker Swarm environments with read-only tools by default and optional mutations.
      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

    B3.2/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools target distinct resource-action pairs, but list_images and portainer_list_unused_images overlap in purpose, as do delete_image and portainer_cleanup_unused_images. However, the names and descriptions clearly distinguish 'all' vs 'unused' variants, reducing ambiguity.

    Naming Consistency3/5

    The majority follow a verb_noun pattern (list_, get_, inspect_, start_, stop_, etc.), but the two tools prefixed with portainer_ (portainer_list_unused_images, portainer_cleanup_unused_images) break the pattern. The mix of list/get/inspect verbs is also slightly inconsistent, though still readable.

    Tool Count4/5

    18 tools is on the heavier side but reasonable for a Docker/Portainer management server covering environments, containers, images, stacks, networks, and volumes. Each tool serves a distinct purpose, with no apparent duplication.

    Completeness3/5

    The toolset covers container lifecycle (start/stop/restart/recreate), image management (pull/delete/cleanup), and stack inspection, but lacks container removal, stack create/update/delete, and network/volume mutations. These are notable gaps for a comprehensive Portainer manager.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources