Allows for automated website deployment to 1Panel servers, including creating websites if they don't exist, uploading static website files, and providing deployment statistics.
Provides video demonstration capabilities, with a specific demo video hosted on Bilibili showcasing the 1Panel deployment functionality.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@1Panel MCP Server deploy my portfolio site to 1panel with domain=portfolio.example.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A Model Context Protocol (MCP) server for automated website deployment to 1Panel.
Currently, this project is an experimental project and does not mean that it can be used directly.
https://www.bilibili.com/video/BV1SjQRY3EmM/
Related MCP server: mcp-1panel
Automates website deployment to 1Panel servers
Creates websites if they don't already exist
Uploads static website files to 1Panel
Fully compatible with the MCP standard protocol
To use this server with Cursor IDE, add the following MCP configuration:
Open Cursor
Create .cursor/mcp.json
{
"mcpServers": {
"1panel-mcp": {
"command": "npx",
"args": [
"-y",
"1panel-mcp"
],
"env": {
"ONEPANEL_BASE_URL": "<your 1Panel base URL>",
"ONEPANEL_API_KEY": "<your 1Panel API key>",
"ONEPANEL_API_VERSION": "v2" // optional, default is v2
}
}
}
}In Cursor, you can deploy websites using the following command in the AI chat:
Deploy to 1Panel with domain=yourdomain.comOr you can use the following format:
Deploy website to 1Panel server, domain: yourdomain.comDeploys a website to 1Panel.
Parameters:
domain (required): Website domain
buildDir (optional): Build directory path
Response:
Successfully deployed to 1Panel!
Domain: yourdomain.com
URL: http://yourdomain.com
Upload statistics:
- Total files: 25
- Successfully uploaded: 25
- Failed to upload: 0Check Build Directory: Verifies if the specified build directory exists
Website Creation: Creates a new static website through 1Panel API if it doesn't exist
File Upload: Uploads all files from the build directory to the website
Statistics: Returns detailed statistics about the upload process
If you encounter deployment issues, check the following:
Ensure your API Key is valid and has sufficient permissions
Verify that the website directory exists and has write permissions
Check the 1Panel server logs for more detailed error information
If file uploads fail, it may be due to file permission or format issues
Deploy website to 1Panel server
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Website domain | |
| buildDir | Yes | Build directory name (e.g. /Users/username/project/dist, /Users/username/project/build) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions deployment but fails to describe what this entails—whether it's destructive, requires authentication, has side effects, or involves rate limits. This leaves critical behavioral traits unspecified.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence with zero wasted words. It is appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of a deployment tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits, return values, or error handling, making it insufficient for an agent to fully understand the tool's operation and implications.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, clearly documenting both parameters. The description adds no additional meaning beyond what the schema provides, such as format examples or constraints, so it meets the baseline for high schema coverage without enhancing parameter understanding.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Deploy') and target ('website to 1Panel server'), providing a specific verb+resource combination. However, without sibling tools, it cannot demonstrate differentiation from alternatives, which prevents a perfect score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description offers no guidance on when to use this tool versus alternatives, prerequisites, or contextual constraints. It merely states what the tool does without any usage context, which is a significant gap.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
deploy_websiteWith only one tool, there is no possibility of confusion or overlap between tools, as there are no other tools to compare it against. The tool's purpose is clearly defined and distinct by default.
The single tool name follows a clear verb_noun pattern (deploy_website), which is consistent within the set. Since there is only one tool, there is no inconsistency to evaluate.
A single tool is too few for a server named '1Panel MCP Server', which implies broader panel management capabilities beyond just website deployment. This minimal toolset feels thin and under-scoped for the apparent domain.
The tool surface is severely incomplete for a panel server, lacking essential operations like managing servers, applications, databases, or monitoring. With only a deploy_website tool, there are significant gaps that will cause agent failures in handling typical panel tasks.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Build, edit, host, and publish websites from AI assistants. Setup: https://mcp.orivox.org/
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
MCP server for building and testing AI agents with multi-model experimentation and insights.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ruibaby/1panel-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
