Un servidor de Protocolo de Contexto de Modelo (MCP) para la implementación automatizada de sitios web en 1Panel.
[!IMPORTANTE] Actualmente este proyecto es un proyecto experimental y no significa que pueda utilizarse directamente.
https://www.bilibili.com/video/BV1SjQRY3EmM/
Related MCP server: mcp-1panel
Automatiza la implementación de sitios web en servidores 1Panel
Crea sitios web si aún no existen
Sube archivos de sitios web estáticos a 1Panel
Totalmente compatible con el protocolo estándar MCP
Para utilizar este servidor con Cursor IDE, agregue la siguiente configuración de MCP:
Cursor abierto
Crear .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>"
}
}
}
}En Cursor, puedes implementar sitios web usando el siguiente comando en el chat de IA:
Deploy to 1Panel with domain=yourdomain.comO puede utilizar el siguiente formato:
Deploy website to 1Panel server, domain: yourdomain.comImplementa un sitio web en 1Panel.
Parámetros:
domain (obligatorio): Dominio del sitio web
buildDir (opcional): ruta del directorio de compilación
Respuesta:
Successfully deployed to 1Panel!
Domain: yourdomain.com
URL: http://yourdomain.com
Upload statistics:
- Total files: 25
- Successfully uploaded: 25
- Failed to upload: 0Verificar directorio de compilación : verifica si existe el directorio de compilación especificado
Creación de sitio web : crea un nuevo sitio web estático a través de la API de 1Panel si no existe
Carga de archivos : carga todos los archivos del directorio de compilación al sitio web
Estadísticas : Devuelve estadísticas detalladas sobre el proceso de carga.
Si encuentra problemas de implementación, verifique lo siguiente:
Asegúrese de que su clave API sea válida y tenga permisos suficientes
Verifique que el directorio del sitio web exista y tenga permisos de escritura
Consulte los registros del servidor 1Panel para obtener información de error más detallada
Si la carga de archivos falla, puede deberse a problemas de permisos o formato del archivo.
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.
deploy_websiteScored across 1 tool
With 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.
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.
