RobotStudioMCP
Automates ABB RobotStudio by managing RobotStudio lifecycle (start/stop), installing/uninstalling .rspak packages, verifying add-in readiness, and exposing station-readiness tools such as checking the active station and listing assemblies. It can also launch RobotStudio with a custom add-in under development and track its load state independently.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
RobotStudioMCP
An MCP server and CLI for automating ABB RobotStudio.
A watchdog (
RobotStudioMCP.Watchdog) that runs as a separate process, manages RobotStudio's lifecycle (start/stop), handles.rspakpackage install/uninstall, and verifies the MCP add-in's readiness — exposed both as an MCP stdio server and as a CLI. For add-in developers: it can also launch RobotStudio with an add-in you're developing and track its load state independently, as a dev-loop tool. The watchdog is the only process that speaks MCP to external clients.A core add-in (
RobotStudioMCP.AddinMain) that runs inside RobotStudio and exposes station-readiness tools (check_active_station,robotstudio_assembly_list), with a plugin seam for optional station-editing tool modules. The add-in doesn't speak MCP itself — it exposes its tools over an internal named pipe that the watchdog forwards calls through, since RobotStudio's own process never declares the ASP.NET Core shared framework an in-process MCP/HTTP server would need.
Prerequisites
RobotStudio 2026
.NET 10 SDK
The
Lagun271.RobotStudio.*NuGet packages (Sdk.Ref,RspakTool), published publicly fromLagun271/robotstudio-sdk-nuget.
Related MCP server: OpenFab MCP
Install
Add-in — build and install the .rspak distribution package:
dotnet build .\src\RobotStudioMCP.AddinMain\RobotStudioMCP.AddinMain.csproj -c Debug
dotnet msbuild .\src\RobotStudioMCP.AddinMain\RobotStudioMCP.AddinMain.csproj -t:PackRspak -p:Configuration=Debug -p:RspakVersion=0.1.0This produces RobotStudioMCP-<version>.rspak — install it via RobotStudio's Package Manager.
Watchdog — build it and add the output folder to PATH:
dotnet build .\src\RobotStudioMCP.Watchdog\RobotStudioMCP.Watchdog.csproj -c DebugOutput: src\RobotStudioMCP.Watchdog\bin\Debug\net10.0\RobotStudioMCP.Watchdog.exe.
Quick start
CLI — start RobotStudio and wait until the add-in is ready:
RobotStudioMCP.Watchdog.exe start --wait-readyMCP — point an MCP client at the watchdog's stdio server (RobotStudioMCP.Watchdog.exe mcp, or no arguments). It exposes lifecycle/readiness/package tools directly, and forwards the add-in's station-readiness tools (check_active_station, robotstudio_assembly_list) over its internal pipe to the running add-in — there is no separate endpoint to point at for those.
Developing your own add-in
Launch RobotStudio with an add-in you're building, and track its load state independently of the installed MCP add-in — no need to install it first. Try it with the repo's own test fixture:
dotnet build .\test\DummyRobotStudioAddin\DummyRobotStudioAddin.csproj -c Debug
RobotStudioMCP.Watchdog.exe start --rsaddin-path "<repo>\test\DummyRobotStudioAddin\bin\Debug\net10.0-windows\DummyRobotStudioAddin.rsaddin" --wait-ready(Use the path under bin\Debug\net10.0-windows\, not the one next to the .csproj — see the note below.)
The JSON response's runtimeReadiness carries both load states independently: mcpAddinLoad for the installed MCP add-in, rsaddinLoad for the one you just pointed at.
Note: --rsaddin-path must point at an .rsaddin file with its assembly in the same folder — RobotStudio resolves <Assembly><FileName> relative to the manifest's own directory, not the project source tree. For an SDK-style project, that's the dotnet build output folder, not the one next to the .csproj.
Learn more
docs/architecture.md— component map, transport choices, plugin model, readiness handshake.docs/mcp-cli-conventions.md— MCP tool naming/result conventions, CLI conventions.
License
MIT — see LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Official Rewst MCP server: build, run, and debug Rewst workflows, forms, apps, and integrations.
mtdt.io MCP: Salesforce DevOps platform connector (metadata deployments, backups and more)
Start and manage Reason cloud coding agents, projects and sessions from any MCP client.
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
Related MCP Servers
- AlicenseBqualityCmaintenanceMCP server for ABB RobotStudio and robot controllers, exposing 55 tools via SDK and RWS transports for simulation, programming, and monitoring.6534MIT
- AlicenseAqualityBmaintenanceEnables offline-first industrial manufacturing workflows by parsing, linting, and drafting FANUC .LS robot programs and analyzing STEP/STP CAD files through MCP tools.4Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to automate CODESYS V3 PLC development, including project editing, builds, library and alarm management, online variable read/write/force operations, and CODESYS documentation search via MCP.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables Roblox Studio workflow automation beyond the built-in MCP, including opening places, managing assets via Open Cloud, safe Luau execution, and extracting place contents.51 npm2MIT