mcpField
M
MegaCloud MCP Server

MegaCloud MCP Server

Local
github.com/megaeaseCloud & Infra1Updated 72w ago

About MegaCloud MCP Server

MegaCloud MCP Server connects MCP clients to the MegaCloud API for middleware and host administration. It supports lifecycle operations, configuration and status checks, backups, and node management, including Redis deployment and scaling.

Key features

  1. 01List hosts and middleware types
  2. 02Create and manage Redis instances
  3. 03Start, stop, restart, and delete middleware
  4. 04Inspect configuration and status
  5. 05Back up middleware instances
  6. 06Manage instance nodes

Use cases

  1. 01Check hosts available for deployment
  2. 02Deploy a Redis instance or cluster
  3. 03Inspect middleware status and configuration
  4. 04Back up an instance or adjust its nodes

MCP support

It exposes MegaCloud API operations as tools for MCP clients, covering hosts, middleware instances, backups, and node management.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

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

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>"
        }
    }
}

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.