CloudNet MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLOUDNET_URL | No | The URL to the CloudNet REST API (default: http://127.0.0.1:2812/api/v3) | http://127.0.0.1:2812/api/v3 |
| CLOUDNET_USER | Yes | The basic auth username | |
| CLOUDNET_PASSWORD | Yes | The basic auth password |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_nodesA | List all nodes in the CloudNet cluster |
| get_node_infoB | Get detailed information about a specific node |
| get_servicesA | List all smart services |
| get_online_playersB | Get a list of online players based on the query parameters |
| get_player_infoB | Get a player by their unique id or name |
| kick_playerC | Kicks a given player from the entire network |
| send_player_messageB | Sends a chat message to a given player |
| execute_player_commandC | Executes a command for a given player |
| execute_service_commandC | Executes the specified command on a service console |
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 9 tools
Each tool targets a distinct action: player vs service commands, node info vs list, player info vs online list, kick vs message. No overlap.
All tools follow a consistent verb_noun pattern in snake_case: execute, get, kick, send. Naming is predictable.
9 tools is well-scoped for a cluster management server covering nodes, services, and players. Feels complete without bloat.
Covers essential node listing/info, player operations, and service commands. Missing service lifecycle (create/delete) and node actions, but core workflows are present.