ABB RobotStudio MCP Server
Related Servers
Alternatives to ABB RobotStudio MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceMCP server for ABB RobotStudio and robot controllers, exposing 55 tools via SDK and RWS transports for simulation, programming, and monitoring.531MIT
- AlicenseNot gradedqualityDmaintenanceEnables automating ABB's robotics IDE through a watchdog MCP/CLI and an in-IDE add-in, including lifecycle control, package management, readiness checks, and station-readiness tools.MIT
- AlicenseCqualityAmaintenanceEnables MCP clients to inspect and modify SketchUp models through a local authenticated bridge, covering entity creation and editing, geometry, materials, tags, cameras, scenes, transactions, snapshots, and file or view export. It also offers an optional full SketchUp Ruby API execution channel and batch operations for furniture, architectural, and analysis tasks.371MIT
- AlicenseDqualityCmaintenanceEnables AI clients to control and inspect a Unity Editor through MCP tools for scene and play-mode operations, logs, screenshots, assertions, Lua execution, UI interaction, world observation, and bridge management; advanced UI/Lua/world features require project-specific adapters.41MIT
- AlicenseAqualityDmaintenanceEnables driving Omniverse Kit apps (Isaac Sim, Isaac Lab) over MCP, allowing agents to control simulations, run Python, and call namespace-scoped tools via a single bridge.12MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to watch and drive a running ResInsight, query reservoir simulation models, and render pictures and plots without touching the GUI.GPL 3.0
TDQS
Scored across 63 tools
The set exposes two parallel interfaces (rs_* SDK and rws_* RWS) with many near-duplicate operations: get_modules, read_module, write_module, read/write_variable, get_position, I/O reads/writes, controller status, and event logs. The protocol qualifiers help somewhat, but an agent must still choose between closely overlapping tools, making misselection likely.
Tool names use a predictable snake_case convention with clear rs_/rws_ interface prefixes. There are minor deviations from strict verb_noun form, such as rs_controller_status and rws_execution_state, but the pattern is largely consistent and readable.
63 tools is far beyond a well-scoped MCP surface; the dual SDK/RWS split multiplies overlapping capabilities. This is an extreme count mismatch for practical agent selection, even for a broad robotics domain.
Coverage is broad: station inspection/save, RAPID module and variable access, simulation control, paths/targets, config, collision checks, I/O, filesystem operations, and mastership. Minor gaps exist, such as deleting paths/targets or managing tasks/routines, but core RobotStudio workflows are represented.