MegaCloud MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEGACLOUD_AUTHTOKEN | Yes | Your MegaCloud authentication token |
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 |
|---|---|
| list_available_hostsA | List all available hosts that can be used to deploy middleware. |
| list_middleware_typesA | List all middleware types. |
| list_middleware_instancesB | List all middleware instances that are currently deployed. |
| restart_middlewareC | Restart a middleware instance. |
| stop_middlewareC | Stop a middleware instance. |
| start_middlewareC | Start a middleware instance. |
| delete_middlewareC | Delete a middleware instance. |
| get_middleware_infoA | Get all information of a middleware instance, like configs, nodes, etc. |
| get_middleware_statusB | Get the status of a middleware instance. |
| backup_middlewareC | Backup a middleware instance. |
| list_middleware_instance_nodesC | List all nodes of a middleware instance. |
| remove_middleware_instance_nodesC | Remove nodes from a middleware instance. |
| list_middleware_instance_change_eventsC | List all change events of a middleware instance. |
| list_middleware_instance_alert_rulesC | List all alert rules of a middleware instance. |
| list_middleware_type_support_log_typesD | List all support log types of a middleware instance. |
| list_middleware_instance_logsC | List logs of a middleware instance. |
| list_host_load_monitor_dataC | List load monitor data of given host |
| list_host_net_err_out_monitor_dataC | List net err out monitor data of given host |
| list_host_net_err_in_monitor_dataC | List net err in monitor data of given host |
| list_host_disk_monitor_dataC | List disk monitor data of given host |
| list_host_disk_input_output_monitor_dataC | List disk input output monitor data of given host |
| list_host_net_bytes_sent_monitor_dataC | List net bytes sent monitor data of given host |
| list_host_net_bytes_recv_monitor_dataC | List net bytes recv monitor data of given host |
| list_host_memory_monitor_dataC | List memory monitor data of given host |
| list_host_cpu_monitor_dataC | List cpu monitor data of given host |
| list_middleware_alert_metricsC | List all alert metrics of a middleware instance that can be used to create alert rules. |
| create_middleware_alert_ruleC | Create an alert rule for a middleware instance. |
| start_middleware_alert_ruleC | Start an alert rule for a middleware instance. |
| stop_middleware_alert_ruleB | Stop an alert rule for a middleware instance. |
| delete_middleware_alert_ruleC | Delete an alert rule for a middleware instance. |
| list_middleware_instance_monitor_metric_typesC | List all monitor metric types of a middleware instance, used to list monitor data. |
| list_middleware_instance_monitor_dataC | List monitor data of a middleware instance. |
| create_single_redis_middlewareC | Create a single redis instance. |
| create_redis_cluster_middlewareC | Create a redis cluster middleware instance. |
| add_redis_nodesC | Add nodes to a redis middleware instance. |
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 35 tools
Each tool targets a specific resource or metric, with no obvious overlaps. However, the high granularity (e.g., separate tools for each host metric) could lead to selection errors if an agent misidentifies the exact tool needed.
All tool names use a consistent verb_noun pattern in snake_case (e.g., list_host_cpu_monitor_data, create_single_redis_middleware). Naming is predictable and follows the same convention throughout.
With 35 tools, the server is overly granular. Many host monitor data tools could be parameterized into fewer tools. The count feels heavy for the apparent scope of middleware management and host monitoring.
The tool surface covers CRUD for middleware instances, alert rules, and comprehensive host monitoring. Minor gaps exist (e.g., no tool to update middleware configuration), but core workflows are well-covered.