1panel-mcp

1panel MCP Server

1panel-mcp connects Cursor's AI chat to a deployment workflow for static websites on 1Panel. It serves developers deploying local build files, with website creation and upload reporting, but remains experimental rather than ready for direct use.

Server facts

1panel-mcp

Tech

Runtime / language
node
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
36
Last commit
Data as of

Tags

  • Automation
  • mcp
  • website deployment

Overview

Static website publishing on 1Panel is the focus of 1panel-mcp, with a single tool, deploy_website, exposed through MCP. The tool accepts a required domain and an optional buildDir path. Its workflow checks that the build directory exists, creates a static website through the 1Panel API when one is not already present, and transfers the build files to the website. Deployment reporting includes the domain, website URL, and counts covering total files, successful uploads, and failed uploads.

The documented interaction takes place in Cursor, where users request deployment through AI chat after configuring the MCP connection. Configuration supplies the 1Panel base URL and API key, with an optional API version setting. The project uses Node and stdio transport. Its experimental status is explicit: the documentation cautions against assuming it can be used directly. Troubleshooting guidance centers on API credentials and permissions, the website directory's existence and write access, server logs, and possible file permission or format problems during uploads.

1panel-mcp setup notes

  • 1panel-mcp records stdio only; confirm a network transport upstream before planning remote access.

Related MCP servers