portainer-mcp

Purpose: Managing Portainer and Docker infrastructure manually from AI assistants and automation workflows.

Inferred · not functionally tested

Audience: DevOps engineers and developers managing Portainer environments

Inferred · not functionally tested

Functions: agents, workflow_automation, monitoring

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted, api_only

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: pypi.org · github.com. These links do not verify the individual claims.

portainer-mcp sits in PulseGate's Frameworks & runtimes category. Inferred · not functionally tested: It focuses on managing Portainer and Docker infrastructure manually from AI assistants and automation workflows. Inferred · not functionally tested: portainer-mcp is an open-source project aimed at devOps engineers and developers managing Portainer environments. Basis unknown · not verified: portainer-mcp is open source under the MIT license. Basis unknown · not verified: It runs on the command line and API, and it can be self-hosted.

It is developed by ginkida, and it first shipped in 2026. Development happens publicly on GitHub with 14 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include stack deployment, stack updates, and swarm management. Inferred · not functionally tested: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.