MegaCloud MCP Server
OfficialRelated Servers
Alternatives to MegaCloud MCP Server
No user-submitted related servers found.
Related Servers
AlicenseAqualityAmaintenanceEnables 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- AlicenseAqualityCmaintenanceEnables AI assistants to inspect, create, modify, and manage FiveM/RedM server resources, configuration, backups, and live runtime actions through a secure MCP interface.12MIT
- AlicenseBqualityBmaintenanceEnables 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
- 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.11 npmMIT
- AlicenseAqualityCmaintenanceEnables 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
- FlicenseBqualityNot gradedmaintenanceEnables AI agents to administer MetaMCP instances by managing servers, namespaces, endpoints, and API keys across multiple deployments. Supports full CRUD operations, bulk server imports, cross-instance cloning, and granular tool management through MetaMCP's tRPC API.261-
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.