Skip to content
ReviewRamble

The weekly brief

AI, reviewed, in your inbox.

  • New reviews of tools, models, MCP servers and repos, with the verdict up front
  • Re-checked prices and ratings when something changes
  • New analysis pieces as they are published

Models, agents, MCP servers and the tools actually worth your time.

One email a week. Unsubscribe with the link in any brief. How we use your email

ABB RobotStudio MCP (LiskinLabs)

Community server with 63 tools for RobotStudio and ABB controllers: RAPID, targets, I/O, motors and program start, with no confirmation.

Reviewed by ReviewRamble editors · Updated

Setup docs Open source

Share this page:XLinkedInFacebookRedditWhatsAppEmail

Our rating

3.1/5

Broad and genuinely useful against a virtual controller, but it can switch motors on and start programs on a real ABB robot with nothing but the agent's judgement in between.

What is ABB RobotStudio MCP (LiskinLabs)?

ABB RobotStudio MCP, LiskinLabs edition, connects an MCP client to ABB RobotStudio and to ABB robot controllers (IRC5, OmniCore and virtual controllers). It has 63 tools in two groups. The 33 rs_ tools reach RobotStudio through a C# add-in: stations, paths and targets, RAPID modules and variables, I/O signals, controller configuration, simulation control, collision checks and screenshots. The 30 rws_ tools call Robot Web Services on the controller: motors on and off, program start and stop, speed override, RAPID modules and variables, I/O, the controller file system, mastership and the event log.

It is a rework by Silvestr Liskin of eliasbitsch/abb-robotstudio-mcp, which has more stars (about 14 against 3) but a single commit, from 8 May 2026, so we chose this actively developed edition. Its last release, v3.1.0, landed on 23 October 2026. The licence file is MIT, though the README says ISC. Neither project is affiliated with ABB.

How to install ABB RobotStudio MCP (LiskinLabs)

git clone https://github.com/LiskinLabs/abb-robotstudio-mcp.git && npm install && npm run build && dotnet build addin/ClaudeBridge.csproj -c Release

Is ABB RobotStudio MCP (LiskinLabs) worth it?

This server can move an industrial robot. rws_set_motors turns motors on, rws_start_program runs RAPID, and rws_write_io and rws_write_variable change signals and data on whatever controller ABB_RWS_URL points to. The allow-list of controller hosts includes 192.168.125.1, the address the README calls a real ABB controller, by default, and rws_set_controller_url switches from a virtual controller to a real one at runtime. None of the 63 tools carries a read-only or destructive annotation, and the server asks for no confirmation, so the only human gate is whatever your MCP client prompts for.

The safety features it does have are narrower than the README's "Zero-Accident Policy" heading suggests. Before rws_start_program and rs_start_simulation run, the server scans the controller event log for active RAPID and syntax errors and refuses to start if it finds any, unless the agent passes force=true. rs_validate_rapid is a structural check, not ABB's RAPID compiler. File operations reject .. paths and the $SYSTEM partition. None of this knows where a person is standing, whether a path clears a fixture or what speed is safe; that remains the job of the controller's own safety system, the cell's guarding and the people responsible for it.

The catch: this is a three-star project with one maintainer, about nine commits and a single test file for the RAPID validator. It was tested with RobotStudio 2025 and virtual IRC5 and OmniCore controllers on Windows 11. Installation means building a TypeScript server and a C# add-in from source. The add-in's bridge listens on 127.0.0.1:58080 with no authentication, and the default Robot Web Services credentials are ABB's factory ones, which you must replace for a real controller.

Our take: point it at a virtual controller in RobotStudio and it is a capable assistant for reading stations, inspecting RAPID and drafting targets and paths. Anything that leaves the simulator should go through a robot programmer, a risk assessment and the usual commissioning sign-off.

Where it earns its place

  • A robot programmer at a system integrator

    Find out why a virtual controller stopped mid-cycle

    Ask the agent to read the event log, execution errors and the RAPID module at the program pointer, then explain the fault. Read-only work against a virtual controller carries no physical risk and saves hunting through logs.

  • A manufacturing engineer planning a new pick-and-place cell

    Draft targets and a path in RobotStudio for a first simulation

    Have the agent create targets and a path, write a RAPID module, validate it and run the simulation with collision checks on a virtual controller. The result is a draft for a programmer to correct, not a program to load on the real robot.

  • A robotics instructor at a technical college

    Show students how RAPID variables and I/O signals relate to program flow

    Let students ask the agent to list and change variables and simulated I/O on a virtual controller and watch the effect. Keep ABB_RWS_ALLOWED_HOSTS free of real controllers in the lab configuration.

Before you commit

Setup
Windows with RobotStudio and a station with a virtual controller. Clone, npm install and npm run build for the server, dotnet build for the C# add-in, run install-addin.ps1, then add dist/index.js to the MCP client with ABB_BRIDGE_URL, ABB_RWS_URL, ABB_RWS_USER and ABB_RWS_PASS.
Integrations
33 rs_ tools over the RobotStudio SDK add-in and 30 rws_ tools over Robot Web Services, stdio transport. Supports IRC5, OmniCore and virtual controllers; Digest authentication for real controllers.
Data and privacy
Runs locally; station and RAPID data go to your model provider. The add-in listens on 127.0.0.1:58080 with no authentication. Controller credentials sit in the MCP client config and default to ABB's factory login. Commands sent to a real controller act on physical machinery.
Cost at scale
Free. Each seat needs a RobotStudio licence from ABB; prices are not published in the project's documentation.
Limits
Tested only with RobotStudio 2025 and virtual controllers on Windows 11. The RAPID validator is structural, not ABB's compiler. One test file; no published releases on GitHub beyond the v3.1.0 commit.

What’s good

  • 63 tools across RobotStudio SDK and Robot Web Services
  • Pre-start check blocks runs with active RAPID errors
  • Controller host allow-list and path traversal checks
  • Add-in installs without administrator rights

What’s not

  • Can switch motors on and start programs with no confirmation
  • Real controller address allowed by default
  • Safety check can be bypassed with force=true
  • Build from source; three stars and one maintainer

Best for

Robot programmers who work in RobotStudio with virtual controllers and want an agent to inspect stations and RAPID, with every change to a real cell approved and commissioned by a qualified engineer.

ABB RobotStudio MCP (LiskinLabs) alternatives

ABB RobotStudio MCP (LiskinLabs): common questions

Is ABB RobotStudio MCP (LiskinLabs) worth it?
Broad and genuinely useful against a virtual controller, but it can switch motors on and start programs on a real ABB robot with nothing but the agent's judgement in between. We rate it 3.1 out of 5.
How much does ABB RobotStudio MCP (LiskinLabs) cost?
Free and open source (MIT licence file; the README says ISC). Requires ABB RobotStudio, commercial software licensed separately by ABB, and an ABB controller or virtual controller.
What are the downsides of ABB RobotStudio MCP (LiskinLabs)?
Can switch motors on and start programs with no confirmation; real controller address allowed by default; safety check can be bypassed with force=true; build from source; three stars and one maintainer.
Who is ABB RobotStudio MCP (LiskinLabs) best for?
Robot programmers who work in RobotStudio with virtual controllers and want an agent to inspect stations and RAPID, with every change to a real cell approved and commissioned by a qualified engineer.
How much does ABB RobotStudio MCP (LiskinLabs) cost for a team or in production?
Free. Each seat needs a RobotStudio licence from ABB; prices are not published in the project's documentation.
Is ABB RobotStudio MCP (LiskinLabs) safe for company data?
Runs locally; station and RAPID data go to your model provider. The add-in listens on 127.0.0.1:58080 with no authentication. Controller credentials sit in the MCP client config and default to ABB's factory login. Commands sent to a real controller act on physical machinery.
What are the best ABB RobotStudio MCP (LiskinLabs) alternatives?
The closest alternatives we have reviewed are ROS MCP Server and WLKATA MT4 control stack.

Answers checked Nov 18, 2026.