Skip to main content
Glama
LiskinLabs

ABB RobotStudio MCP Server

by LiskinLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to ABB RobotStudio MCP Server

No user-submitted related servers found.

    Related Servers

    • RobotStudioMCP

      Lagun271
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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

    • robot-structural-mcp

      TranTriLuc
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Autodesk Robot Structural Analysis Professional that enables AI assistants to read model data, loads, and analysis results from an open Robot session, with optional write and calculation tools.
      1
      -

    • nrs_llm

      eunseopsong
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for ROS 2 environments that connects via rosbridge WebSocket, enabling topic/service introspection, publish/subscribe, service calls, robot connectivity checks, and polishing pipeline operations.
      Apache 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3/5.0

    Scored across 53 tools

    Disambiguation4/5

    Tools are clearly grouped by prefix (rs_ for RobotStudio SDK, rws_ for Robot Web Services), which helps an agent differentiate between simulation and real controller operations. However, some functions like rs_controller_status and rws_controller_status overlap in purpose, though descriptions clarify the different access methods.

    Naming Consistency5/5

    All tools consistently use snake_case with the rs_ or rws_ prefix. Verbs such as get, set, read, write, start, stop are uniformly applied, making the naming predictable and easy to follow.

    Tool Count4/5

    53 tools is a high count, but it is justified by the dual nature of the server covering both RobotStudio simulation and RWS real controller operations. Each sub-domain has a reasonable number of tools for its complexity, though the total might be slightly overwhelming for an agent.

    Completeness4/5

    The tool set covers a broad range of operations: station management, simulation control, path/target manipulation, I/O, file system, program execution, and variable reading/writing via both SDK and RWS. Minor gaps like deployment or user management are acceptable given the focus on programming and control.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources