MegaCloud MCP Server
OfficialProvides tools for managing Redis middleware instances on the MegaCloud platform, including creating single Redis instances, Redis clusters, adding nodes, and performing lifecycle operations.
Click on "Deploy 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., "@MegaCloud MCP Server list available hosts"
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.
MegaCloud MCP Server
MCP Server for the MegaCloud API, enabling middleware management, information checking, and more.
Features
Host checking
Middleware lifecycle (create, start, stop, restart, delete, add node, delete node)
Status and configuration inspection
Backups
Node-level management
Tools
Below is the list of your MCP tools converted into the requested format:
list_available_hostsList all available hosts that can be used to deploy middleware.
Inputs: None
Returns: List of host objects.
list_middleware_typesList all middleware types.
Inputs: None
Returns: List of supported middleware‐type identifiers.
list_middleware_instancesList all middleware instances that are currently deployed.
Inputs: None
Returns: List of middleware instance objects
restart_middlewareRestart a middleware instance.
Inputs:
middleware_instance_name(string): Middleware Instance Name
Returns: Operation result / status confirmation
stop_middlewareStop a middleware instance.
Inputs:
middleware_instance_name(string): Middleware Instance Name
Returns: Operation result / status confirmation
start_middlewareStart a middleware instance.
Inputs:
middleware_instance_name(string): Middleware Instance Name
Returns: Operation result / status confirmation
delete_middlewareDelete a middleware instance.
Inputs:
middleware_instance_name(string): Middleware Instance Name
Returns: Operation result / deletion confirmation
get_middleware_infoGet all information of a middleware instance, like configs, nodes, etc.
Inputs:
middleware_instance_name(string): Middleware Instance Name
Returns: Detailed middleware-instance object
get_middleware_statusGet the status of a middleware instance.
Inputs:
middleware_instance_name(string): Middleware Instance Name
Returns: Status object (e.g. running/stopped + node list)
backup_middlewareBackup a middleware instance.
Inputs:
middleware_instance_name(string): Middleware Instance Name
Returns: Backup task details / confirmation
list_middleware_instance_nodesList all nodes of a middleware instance.
Inputs:
middleware_instance_name(string): Middleware Instance Name
Returns: Array of node objects
remove_middleware_instance_nodesRemove nodes from a middleware instance.
Inputs:
name(string): Name of the middleware instancenode_names(array[string]): Node Names to remove
Returns: Operation result / updated node list
create_single_redis_middlewareCreate a single Redis instance.
Inputs:
host_name(string): Host Name (required)max_memory_in_gb(integer, default 4): Max Memory In GBname(string | null, default null): Instance Name (optional)
Returns: Newly created middleware-instance object
create_redis_cluster_middlewareCreate a Redis Cluster middleware instance.
Inputs:
name(string | null, default null): Cluster Name (optional)max_memory_in_gb(integer, default 4): Max Memory In GB per nodemaster_host_names(array[string]): Master Host Names (required)replica_host_names(array[string]): Replica Host Names (required)
Returns: Newly created cluster-instance object
add_redis_nodesAdd nodes to a Redis middleware instance.
Inputs:
name(string): Name of the Redis instance (required)master_host_names(array[string] | null, default null): New Master Hosts (optional)replica_host_names(array[string] | null, default null): New Replica Hosts (optional)
Returns: Operation result / updated cluster topology
Related MCP server: openserverless-mcp
Setup
Obtain an Auth Token
Log in to the MegaCloud console, open your browser’s Network tab while loading any API call, and extract the Authorization: Bearer <token> header value.
Install
Clone the repo:
git clone https://github.com/megaease/megacloud-mcp.gitThen run
pip install "mcp[cli]"Remember to install mcp command globally for all users.
VS Code Integration
Cline
Install the Cline for VS Code extension.
Set MegaCloud MCP server with following config:
{
"mcpServers": {
"megacloud-mcp": {
"type": "stdio",
"command": "mcp",
"args": [
"run",
"<your-repo-dir>/megacloud-mcp/megacloud_mcp/__main__.py"
],
"env": {
"MEGACLOUD_AUTHTOKEN": "<your-auth-token>"
}
}
}
}GitHub Copilot
{
"mcp": {
"servers": {
"test-megacloud-mcp": {
"type": "stdio",
"command": "mcp",
"args": [
"run",
"<your-repo-dir>/megacloud-mcp/megacloud_mcp/__main__.py"
],
"env": {
"MEGACLOUD_AUTHTOKEN": "<your-auth-token>"
}
}
}
}
}Run with Docker
Build the image:
docker build -t megaease/megacloud-mcp . Settings:
{
"megacloud-mcp": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"MEGACLOUD_AUTHTOKEN",
"megaease/megacloud-mcp"
],
"env": {
"MEGACLOUD_AUTHTOKEN": "<your-auth-token>"
}
}
}Available Tools
35 toolsadd_redis_nodesC
Add nodes to a redis middleware instance.
Inputs: name (required), master_host_names, replica_host_names.
backup_middlewareC
Backup a middleware instance.
Inputs: middleware_instance_name (required).
create_middleware_alert_ruleC
Create an alert rule for a middleware instance.
Inputs: name (required), description (required), resolved_description (required), middleware_instance_name (required), +6 more.
create_redis_cluster_middlewareC
Create a redis cluster middleware instance.
Inputs: master_host_names (required), replica_host_names (required), name, max_memory_in_gb.
create_single_redis_middlewareC
Create a single redis instance.
Inputs: host_name (required), max_memory_in_gb, name.
delete_middlewareC
Delete a middleware instance.
Inputs: middleware_instance_name (required).
delete_middleware_alert_ruleC
Delete an alert rule for a middleware instance.
Inputs: middleware_instance_name (required), alert_rule_name (required).
get_middleware_infoA
Get all information of a middleware instance, like configs, nodes, etc.
Inputs: middleware_instance_name (required).
get_middleware_statusB
Get the status of a middleware instance.
Inputs: middleware_instance_name (required).
list_available_hostsA
List all available hosts that can be used to deploy middleware.
Inputs: no named parameters.
list_host_cpu_monitor_dataC
List cpu monitor data of given host
Inputs: host_name (required), time_interval_in_minutes.
list_host_disk_input_output_monitor_dataC
List disk input output monitor data of given host
Inputs: host_name (required), time_interval_in_minutes.
list_host_disk_monitor_dataC
List disk monitor data of given host
Inputs: host_name (required), time_interval_in_minutes.
list_host_load_monitor_dataC
List load monitor data of given host
Inputs: host_name (required), time_interval_in_minutes.
list_host_memory_monitor_dataC
List memory monitor data of given host
Inputs: host_name (required), time_interval_in_minutes.
list_host_net_bytes_recv_monitor_dataC
List net bytes recv monitor data of given host
Inputs: host_name (required), time_interval_in_minutes.
list_host_net_bytes_sent_monitor_dataC
List net bytes sent monitor data of given host
Inputs: host_name (required), time_interval_in_minutes.
list_host_net_err_in_monitor_dataC
List net err in monitor data of given host
Inputs: host_name (required), time_interval_in_minutes.
list_host_net_err_out_monitor_dataC
List net err out monitor data of given host
Inputs: host_name (required), time_interval_in_minutes.
list_middleware_alert_metricsC
List all alert metrics of a middleware instance that can be used to create alert rules.
Inputs: middleware_type_name (required).
list_middleware_instance_alert_rulesC
List all alert rules of a middleware instance.
Inputs: middleware_instance_name (required).
list_middleware_instance_change_eventsC
List all change events of a middleware instance.
Inputs: middleware_instance_name (required).
list_middleware_instance_logsC
List logs of a middleware instance.
Inputs: middleware_instance_name (required), log_type (required), time_interval_in_minutes, current_page.
list_middleware_instance_monitor_dataC
List monitor data of a middleware instance.
Inputs: middleware_instance_name (required), node_name (required), metric_name (required), time_interval_in_minutes.
list_middleware_instance_monitor_metric_typesC
List all monitor metric types of a middleware instance, used to list monitor data.
Inputs: middleware_instance_name (required).
list_middleware_instance_nodesC
List all nodes of a middleware instance.
Inputs: middleware_instance_name (required).
list_middleware_instancesB
List all middleware instances that are currently deployed.
Inputs: no named parameters.
list_middleware_typesA
List all middleware types.
Inputs: no named parameters.
list_middleware_type_support_log_typesD
List all support log types of a middleware instance.
Inputs: middleware_type_name (required).
remove_middleware_instance_nodesC
Remove nodes from a middleware instance.
Inputs: name (required), node_names (required).
restart_middlewareC
Restart a middleware instance.
Inputs: middleware_instance_name (required).
start_middlewareC
Start a middleware instance.
Inputs: middleware_instance_name (required).
start_middleware_alert_ruleC
Start an alert rule for a middleware instance.
Inputs: middleware_instance_name (required), alert_rule_name (required).
stop_middlewareC
Stop a middleware instance.
Inputs: middleware_instance_name (required).
stop_middleware_alert_ruleB
Stop an alert rule for a middleware instance.
Inputs: middleware_instance_name (required), alert_rule_name (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Deploy and manage Edge Network cloud: sites, VMs, storage, DNS, Shield, Assist. Agent self-signup.
EU cloud as MCP tools: VPS, databases, caches, storage, containers and more. Takes an API token.
Official xCloud MCP: manage servers, sites, WordPress, SSL, backups and deploys from any MCP client.
Manage brainCloud apps, cloud code, hooks and servers; API lookups to help generate client code.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to manage a Remnawave panel through its full API, covering users, nodes, hosts, subscriptions, and more with configurable tool profiles and read/write token access.18 npmMIT
- AlicenseAqualityDmaintenanceEnables MCP-capable agents to create and invoke OpenServerless endpoints, manage secrets, and configure integrations such as S3, PostgreSQL, Redis, Milvus, and MongoDB.13Apache 2.0

meshive-mcpofficial
AlicenseAqualityBmaintenanceEnables MCP-capable agents to manage Meshive GPU Cloud resources, including account, workspaces, pods, storage, GPUs, templates, serverless deployments, tasks, assets, machines, and billing history.44Apache 2.0- AlicenseBqualityCmaintenanceEnables MCP clients to control an infra-TAK host, including marketplace modules, Node-RED flows, MediaMTX video, TAK video publishing, and Docker operations via local APIs.19MIT