Parallels RAS MCP Server
Related Servers
Alternatives to Parallels RAS MCP Server
No user-submitted related servers found.
Related Servers
AlicenseAqualityDmaintenanceRead-only MCP server that allows AI assistants to query and monitor KVM Fleet devices, audit logs, and console sessions through the official REST API.516 npm1MIT- AlicenseAqualityDmaintenanceA read-only MCP server for Proxmox VE that provides AI assistants with structured visibility into cluster nodes, guests, storage, and Docker workloads. It is designed to prevent any mutating operations by construction.12MIT
- FlicenseBqualityCmaintenanceA secure, read-only MCP server that enables AI assistants to inspect transactions, vendor performance, wallet balances, and analytics through validated REST API calls.19-
- AlicenseAqualityBmaintenanceAn MCP server that gives AI assistants safe, read-only visibility into a host: CPU, memory, disk, processes, network, ports, and logs.8MIT
- AlicenseNot gradedqualityDmaintenanceA read-only MCP server that provides tools to list and read devices, MDM servers, blueprints, configurations, apps, packages, users, and other resources from Apple Business Manager and Apple School Manager.MIT
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server that lets AI assistants diagnose Dell SC Series storage arrays through the array's own REST API.MIT
TDQS
Scored across 43 tools
Tools are mostly organized by distinct RAS domains (farm, site, infra, pub) and resource types, making purposes clear. However, ras_pub_get_all_items overlaps with the specialized app, desktop, and folder listing tools, creating some ambiguity about when to use the aggregate versus targeted getters.
All tools use a consistent ras_<domain>_<verb>_<resource> pattern with snake_case, which is highly predictable. The minor inconsistency is that listing operations sometimes use get (e.g., ras_infra_get_agents) and sometimes list (e.g., ras_sessions_list, ras_policies_list).
43 tools is well above the typical 3-15 range and exceeds the 25+ threshold where count becomes a usability concern. Many granular getters for individual settings could be consolidated or parameterized without losing functionality.
The tool surface is entirely read-only: every tool is a get, list, or search operation. There are no create, update, delete, or action tools for any RAS resource, so agents cannot perform lifecycle management or remediation tasks, leaving significant gaps for an administration-focused server.