Skip to main content
Glama
MegaCloud MCP Server

MegaCloud MCP Server

Official
by megaease

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:

  1. list_available_hosts

    • List all available hosts that can be used to deploy middleware.

    • Inputs: None

    • Returns: List of host objects.

  2. list_middleware_types

    • List all middleware types.

    • Inputs: None

    • Returns: List of supported middleware‐type identifiers.

  3. list_middleware_instances

    • List all middleware instances that are currently deployed.

    • Inputs: None

    • Returns: List of middleware instance objects

  4. restart_middleware

    • Restart a middleware instance.

    • Inputs:

      • middleware_instance_name (string): Middleware Instance Name

    • Returns: Operation result / status confirmation

  5. stop_middleware

    • Stop a middleware instance.

    • Inputs:

      • middleware_instance_name (string): Middleware Instance Name

    • Returns: Operation result / status confirmation

  6. start_middleware

    • Start a middleware instance.

    • Inputs:

      • middleware_instance_name (string): Middleware Instance Name

    • Returns: Operation result / status confirmation

  7. delete_middleware

    • Delete a middleware instance.

    • Inputs:

      • middleware_instance_name (string): Middleware Instance Name

    • Returns: Operation result / deletion confirmation

  8. get_middleware_info

    • Get all information of a middleware instance, like configs, nodes, etc.

    • Inputs:

      • middleware_instance_name (string): Middleware Instance Name

    • Returns: Detailed middleware-instance object

  9. get_middleware_status

    • Get the status of a middleware instance.

    • Inputs:

      • middleware_instance_name (string): Middleware Instance Name

    • Returns: Status object (e.g. running/stopped + node list)

  10. backup_middleware

    • Backup a middleware instance.

    • Inputs:

      • middleware_instance_name (string): Middleware Instance Name

    • Returns: Backup task details / confirmation

  11. list_middleware_instance_nodes

    • List all nodes of a middleware instance.

    • Inputs:

      • middleware_instance_name (string): Middleware Instance Name

    • Returns: Array of node objects

  12. remove_middleware_instance_nodes

    • Remove nodes from a middleware instance.

    • Inputs:

      • name (string): Name of the middleware instance

      • node_names (array[string]): Node Names to remove

    • Returns: Operation result / updated node list

  13. create_single_redis_middleware

    • Create a single Redis instance.

    • Inputs:

      • host_name (string): Host Name (required)

      • max_memory_in_gb (integer, default 4): Max Memory In GB

      • name (string | null, default null): Instance Name (optional)

    • Returns: Newly created middleware-instance object

  14. create_redis_cluster_middleware

    • Create 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 node

      • master_host_names (array[string]): Master Host Names (required)

      • replica_host_names (array[string]): Replica Host Names (required)

    • Returns: Newly created cluster-instance object

  15. add_redis_nodes

    • Add 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.git

Then 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 tools
add_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

    C2.8/5.0

    Scored across 35 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness4/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP-capable agents to manage Meshive GPU Cloud resources, including account, workspaces, pods, storage, GPUs, templates, serverless deployments, tasks, assets, machines, and billing history.
      44
      Apache 2.0