Global-MCP-Server
Related Servers
Alternatives to Global-MCP-Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to inspect and control a robotic VLA system via MCP, offering read-only tools for ROS topics, processes, tmux, and logs, as well as write tools for publishing prompts, issuing tmux commands, restarting services, and running shell commands inside containers.-
- AlicenseNot gradedqualityDmaintenanceEnables AI tools to interact with ROS2 robotics systems through natural language commands. Supports topic publishing/subscribing, service calls, message analysis, and auto-discovery of ROS2 interfaces for debugging and controlling robots.Mozilla Public 2.0
- AlicenseAqualityAmaintenanceConnects AI agents to ROS 2 robots via rosbridge, enabling observation, inspection, and control of robot topics, services, and actions through natural language.112MIT
- AlicenseAqualityDmaintenanceEnables controlling robots in ROS environments through natural language, supporting topics, services, actions, and GUI tools.2436MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to interact with ROS1 Noetic robotic systems by providing tools for topic management, service calls, and parameter configuration. It also supports node inspection, coordinate transform queries, and message introspection via the Model Context Protocol.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to securely connect to and manage remote servers via SSH, with tools for running commands, file operations, log inspection, service management, and system monitoring under configurable access controls and audit logging.12617 npmMIT
TDQS
Scored across 11 tools
Most tools target distinct layers: ROS topics, host processes, tmux sessions, log files, and remote hosts. Minor overlap exists between process_status and tmux_status for service verification, and tmux_capture/read_log both retrieve output, but their contexts are clearly described.
There is a mix of patterns: tmux_status, tmux_capture, process_status, and ssh_hosts follow object/action style, while read_log, restart_service, and exec_cmd use action/object style. The prefixes help readability, but the inconsistency prevents a higher score.
11 tools is well-scoped for a server covering ROS monitoring, process/log inspection, tmux interaction, command execution, and remote SSH access. Each tool has a distinct operational purpose and none feel redundant.
The server covers the main diagnostic and operational workflows: checking statuses, reading logs, restarting a service, sending tmux commands, and executing shell commands locally or remotely. It lacks a generic service control lifecycle and remote file operations, but exec_cmd and ssh_exec cover many edge cases.