abb-rws-mcp
Related Servers
Alternatives to abb-rws-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to inspect industrial devices read-only over Modbus TCP and OPC UA, including reading and watching values, browsing nodes, decoding registers, and diagnosing connection issues without any write capability.Apache 2.0
- AlicenseAqualityCmaintenanceEnables AI coding assistants to look up KUKA system variables and KSS alarms, lint and diagnose KRL projects, perform industrial safety audits, and read live controller telemetry from KRC4/KRC5 or virtual controllers.12MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to query RoboShadow's Rubicon Platform Data API for read-only endpoint security, asset inventory, applications, users, vulnerabilities, and remediation status data.401Apache 2.0
- AlicenseBqualityBmaintenanceEnables AI assistants and MCP-compatible clients to inspect MikroTik RouterOS v7 devices through the native REST API for read-only observability, monitoring, diagnostics, and configuration review. It exposes system, interface, routing, DHCP, firewall, and log data without allowing router modifications.12415 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides AI assistants with read-only access to Reddit's API for browsing subreddits, reading posts and comments, searching Reddit, and retrieving user/subreddit information. Enables safe exploration of Reddit content without posting capabilities through natural language interactions.-
- AlicenseAqualityDmaintenanceRead-only Modbus TCP monitoring server that exposes safe MCP tools for AI agents to read holding/input registers, coils, and device identity from industrial devices without write access.4Apache 2.0
TDQS
Scored across 10 tools
Most tools target clearly distinct resources: event log vs. single event, RAPID source vs. variable vs. execution state, I/O, position, controller list. The only real overlap is summarize_controller versus get_controller_status and get_event_log, since the summary re-packages status and recent errors; the descriptions mitigate this with explicit guidance ('Start here', 'For the program text, use read_rapid_source').
All names are snake_case verb_noun with an object that matches the resource, which is highly predictable. The verb choice wobbles slightly for similar operations (read_io_signals / read_rapid_variable versus get_robot_position / get_rapid_execution), but the meaning is never unclear.
Ten tools for a read-only ABB controller monitoring server is well-scoped: one per observable domain (status, events, RAPID, I/O, motion, controller inventory). No tool looks redundant enough to drop.
The read-only surface covers state, events, RAPID execution/source/variables, I/O, and motion with sensible detail levels, so core workflows have no dead ends. A few minor gaps exist, such as no direct way to enumerate RAPID modules or tasks when a module name is not already known from the program pointer.