1Panel MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deploy_websiteC | Deploy website to 1Panel server |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored 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.