ACS MCP Server
Related Servers
Alternatives to ACS MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables secure SSH connections to remote servers for executing shell commands and managing active sessions. It supports authentication via passwords or private keys and provides optional host-based access control.4179 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables agents to access network device management interfaces via SSH, keeping credentials on the server side. Supports both interactive terminal sessions and command execution on devices like Huawei VRP, MikroTik, and OpenWrt.1-
- FlicenseNot gradedqualityDmaintenanceEnables remote management and debugging of AstrBot servers via SSH, including log monitoring, status checks, and command execution.-
- FlicenseNot gradedqualityCmaintenanceEnables remote server management via SSH, including command execution, file transfer (SFTP), and interactive shell sessions, with support for multiple hosts.-
- AlicenseAqualityDmaintenanceEnables remote server management through SSH and SFTP, supporting command execution, file transfers, and interactive shell sessions. It allows for multiple concurrent connections using either password or SSH key authentication.119 npm4MIT
- AlicenseNot gradedqualityDmaintenanceEnables SSH connections and remote command execution with persistent session management and real-time browser-based terminal monitoring. Supports multiple simultaneous SSH sessions with command history tracking and live WebSocket streaming of terminal output.6MIT
TDQS
Scored across 32 tools
Each tool targets a distinct resource and action. While download_config, deploy_config, and push_config have related purposes, their descriptions and distinct parameters (fileUrl vs local path vs push flag) make them separable. No two tools appear to do the same thing.
All tools share the acs_ prefix and mostly follow verb_noun structure. Some stand-alone verbs (start, stop, restart) and nouns (status, connection_request) are minor deviations but the pattern is predictable and readable.
32 tools is heavy for a single server. While the domain is complex (devices, scripts, config, logs), the count exceeds the 25+ threshold and many tools overlap in purpose (e.g., three config-push mechanisms), suggesting some consolidation is possible.
The surface covers server lifecycle, device discovery, script management, parameter access, config deployment, and logging. Minor gaps include no explicit device add/remove or script enable/disable, but core workflows (device connect, configure, reboot) are fully supported.