mcp-1panel is an implementation of the Model Context Protocol (MCP) server for 1Panel.
MCPpedia last refreshed this data
MCP 1panel is an MCP server that mcp-1panel is an implementation of the Model Context Protocol (MCP) server for 1Panel. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 77/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"mcp-1panel": {
"env": {
"PANEL_HOST": "such as http://localhost:8080",
"PANEL_ACCESS_TOKEN": "<your 1Panel access token>"
},
"command": "mcp-1panel"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
1Panel MCP Server is an implementation of the Model Context Protocol (MCP) server for 1Panel.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in devops
MCP server for using the GitLab API
MCP server for discovering, reading, and changing ZenML resources with compact generic tools
MCP server for Dynatrace Managed to access logs, events, and metrics.
An MCP server for Azure DevOps
MCP Security Weekly
Get CVE alerts and security updates for Mcp 1panel and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP server for 1Panel v2, with 20 shared tools for nodes, system status, websites, certificates, applications and MySQL. Independent mode uses the official Go MCP SDK; managed mode integrates with 1Panel's authorization and audit.
| Mode | Connection and authorization | Deployment |
|---|---|---|
Independent: --mode=legacy (default) | Configured API Key calls existing public /api/v2 APIs; panel permissions apply to every request | stdio or Streamable HTTP, as a binary or Docker container |
Managed: --mode=panel | Dedicated MCP credential; Core checks the owner's current permissions, node/tool grants and policy | Docker on the primary node, installed from AI → MCP Management → 1Panel MCP |
Independent mode requires an enabled public API and compatible APIs/DTOs for the selected tools on your installed 1Panel v2 release. It needs no managed MCP installation. Managed mode requires matching Core, primary/child Agents and frontend. See managed deployment.
| Credential | Purpose |
|---|---|
PANEL_ACCESS_TOKEN / --token | 1Panel API Key used by independent mode for outgoing panel requests |
MCP_AUTH_TOKEN / --mcp-token | Separate pre-shared Bearer used by clients connecting to independent Streamable HTTP |
| Token created in the panel's MCP page | Dedicated managed credential with explicit node/tool grants; clients use the panel's HTTPS /mcp endpoint |
The independent HTTP token permits use of the configured API Key; it does not create another panel identity. The two modes' MCP credentials are not interchangeable.
Use Go 1.27.3. The v2 source branch is dev-v2:
git clone --branch dev-v2 https://github.com/1Panel-dev/mcp-1panel.git
cd mcp-1panel
go mod download
make build
./build/mcp-1panel --version
make build creates a host-platform binary at build/mcp-1panel.
To cross-build Linux, use make build_linux GOARCH=amd64 or GOARCH=arm64;
make build_linux_all builds all seven architectures: 386, amd64, arm64, armv7, s390x, ppc64le and riscv64.
Linux builds require a locally available toolchain and cached dependencies;
outputs are build/mcp-1panel-linux-{arch}.
Choose an explicitly published v2 release from Releases
compatible with your installed panel's public APIs. Download the matching architecture
and SHA256SUMS, verify the checksum, then run, for example on Linux amd64:
chmod +x ./mcp-1panel-linux-amd64
./mcp-1panel-linux-amd64 --version
Use that binary's absolute path in the client configuration below.
For maintainers, publishing a GitHub Release triggers tests, builds all seven Linux binaries,
uploads them with SHA256SUMS to that release, and pushes the multi-platform Docker image.
Ordinary commits, tag pushes and saved drafts do not trigger this workflow. The release tag
provides the version; prereleases and tags containing - do not update Docker latest.
The image defaults to independent stdio mode. To build and export a fixed version locally (these commands do not publish an image):
make docker_build VERSION=v2.0.0-rc1 DOCKER_PLATFORM=linux/amd64
make docker_save VERSION=v2.0.0-rc1 DOCKER_PLATFORM=linux/amd64
# Transfer to a matching Linux host, then import:
docker load -i build/mcp-1panel-linux-amd64-v2.0.0-rc1.tar
Choose your own fixed version; the example tag is not a publication claim.
The official repository is 1panel/mcp-server. Docker builds support
linux/386, linux/amd64, linux/arm64, linux/arm/v7, linux/s390x, linux/ppc64le and
linux/riscv64. For managed installation, use the panel's installation dialog and
container contract.
Let the MCP client start the binary;