Portainer MCP Server
Manage Portainer environments, GitOps, and Docker/Kubernetes resources via MCP tools.
Data last scanned today · Reviewed today
Overview
The Portainer MCP server bridges the gap between your AI assistant and your Portainer infrastructure. By exposing the Portainer REST API as a series of MCP tools, it allows users to perform tasks such as listing and inspecting environments, managing GitOps workflows, and troubleshooting Docker and Kubernetes resources directly through their AI agent. Designed for flexibility, the server supports local execution via uvx or MCP bundles, as well as team-based deployments as a container. Users must provide their own Portainer API key, ensuring that all operations are performed under their specific identity within the Portainer platform.
Our verdict
With a security score of 43/100, this server is classified as high-risk. This rating is driven by the fact that the authentication method has not yet been reviewed and the read-only mode status is currently unverified. Because the server can handle sensitive infrastructure operations, it should be used with caution in development environments by experienced users who understand the implications of the transport security requirements for the containerized deployment.
- Zero direct dependencies reduce the supply-chain attack surface.
- Utilizes the FastMCP framework for OpenAPI-based tool generation.
- Actively maintained with a commit within the last week.
- Includes documented support for both stdio and containerized deployments.
- Authentication methods for the server remain unreviewed for risks.
- Read-only operational modes have not been verified.
- Community-maintained rather than managed by the official vendor.
- Requires explicit handling of TLS certificates for secure connections.
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›Does this MCP server require any credentials to function?
Yes, you must generate an API key in your Portainer account under 'My Account → Access tokens' to authenticate your requests.
›How do I ensure compatibility with my Portainer instance?
You should match the MCP server's minor version to your Portainer instance's minor version, such as using version 2.45.x for Portainer 2.45.x.
›Can I use this server with self-signed TLS certificates?
Yes, if your Portainer instance uses self-signed certificates, you must set the environment variable PORTAINER_TLS_VERIFY=0 when running the server.
›What is the purpose of the PORTAINER_MCP_AUTH_TOKEN?
This is a shared gate secret used in HTTP deployments to allow incoming requests; individual user actions are still governed by their own specific Portainer API keys.
›Why might I receive a 421 DNS-rebinding error?
This occurs if the hostname or IP address reaching the MCP server is not included in the PORTAINER_MCP_ALLOWED_HOSTS list.
›Is it safe to expose the MCP server on the public internet?
No, it is not recommended to expose the server on the public internet, and it should be hosted within your private infrastructure.
Alternatives
Changelog
Badge
Maintain this server? Add the live badge to your README.