abb-rws-mcp
Read-only MCP server for diagnosing why an ABB robot controller stopped
- Pricing
- Open source
- Platforms
- Windows, Linux, CLI
- Runs
- Locally
- Version
- 0.2.0
- Listing updated
- today
Similar MCP servers
About abb-rws-mcp
abb-rws-mcp is an open-source MCP server for manufacturing. It runs locally on your machine and is started by your AI client.
abb-rws-mcp never talks to a robot directly. It reads through abb-rws-daemon running on 127.0.0.1 on the same PC, which holds the single session per controller over ABB Robot Web Services, covering RWS 1.0 on IRC5 with RobotWare 6 and RWS 2.0 on OmniCore with RobotWare 7 and 8. The server opens no controller session and never sees controller credentials.
It has ten tools and one prompt and every tool reads. None sets a signal, starts or stops a program, moves a program pointer, edits a module, switches motors, changes speed or requests write access, and there is no write tool hidden behind a flag. The one non-GET request asks the daemon to sample joint positions for 15 seconds. The why_did_it_stop prompt gives the assistant a fixed recipe: summary, problems with ABB's recommended actions, the source line at the program pointer, named signals, the age of each value, and only causes the data supports.
Every answer starts with a status line giving controller id, virtual or real, RobotWare version and whether data is current, degraded, down or a replay, and values carry UTC time and age. Controller text is passed along marked as data, not instructions. The README reports testing on three RobotStudio virtual controllers and notes it has not yet been run against a real controller.
Install
Run in a terminal
claude mcp add abb-rws-mcp -- npx -y abb-rws-mcpAdd to claude_desktop_config.json
{
"mcpServers": {
"abb-rws-mcp": {
"command": "npx",
"args": [
"-y",
"abb-rws-mcp"
]
}
}
}Add to ~/.cursor/mcp.json
{
"mcpServers": {
"abb-rws-mcp": {
"command": "npx",
"args": [
"-y",
"abb-rws-mcp"
]
}
}
}Add to .vscode/mcp.json
{
"servers": {
"abb-rws-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"abb-rws-mcp"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"abb-rws-mcp": {
"command": "npx",
"args": [
"-y",
"abb-rws-mcp"
]
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"abb-rws-mcp": {
"command": "npx",
"args": [
"-y",
"abb-rws-mcp"
]
}
}
}Using several servers? Build one config file with the MCP config generator.
Tools this server provides (10)
Taken from the project documentation; the running server may differ.
- summarize_controller
- State in one sentence, recent errors and warnings with ABB actions, messages and program pointer source lines.
- list_controllers
- Lists the controllers the daemon knows with a state line.
- get_controller_status
- Controller state, operating mode, speed override, collision detection and RAPID execution.
- get_robot_position
- Joint positions, TCP pose and proximity to joint limits via motion sampling.
- read_io_signals
- Signals and values from the daemon's table, or a signal search.
- get_event_log
- Controller event log filtered by severity, time, category or code.
- explain_event
- Lays out one event with ABB's description, causes and actions.
- get_rapid_execution
- Execution state and program and motion pointers per task.
- read_rapid_source
- Reads a module's RAPID source with line numbers.
- read_rapid_variable
- Reads the value of one RAPID data symbol as RAPID text.
What it does
- Strictly read-only
- No tool writes signals, controls programs or requests mastership.
- Controller summary
- Gives state, recent errors with ABB's actions, messages and program pointer lines.
- Event explanation
- Separates what the controller says from the server's own reading of an event.
- RAPID source and variables
- Reads module source with line numbers and individual variable values.
- Timestamps and staleness
- Every value shows UTC time and age, and stale values are labelled.
- Controller text as data
- Messages and names from the controller are marked as data, not instructions.
- Why-did-it-stop prompt
- A fixed diagnostic recipe available as a slash command.
Good for
- Find out why a robot program stopped
- Explain an event-log entry with ABB's recommended actions
- Review the RAPID line at the program pointer
- Check joint positions and distance to limits
- Inspect I/O signals during troubleshooting
Pricing
Open source
Free npm package; requires abb-rws-daemon
abb-rws-mcp FAQ
What do I need to run it?
Node.js 20 or later on Windows or Linux, plus abb-rws-daemon 0.1.1 or a later 0.x on the same PC with a controller already added.
Can it change anything on the robot?
No. All ten tools read; none writes signals, starts or stops programs, or requests write access.
Which controllers are supported?
IRC5 with RobotWare 6 over RWS 1.0, and OmniCore with RobotWare 7 and 8 over RWS 2.0.
Has it been tested on real hardware?
The README says it has been tested on three RobotStudio virtual controllers and not yet on a real controller.
How do I install it?
Add npx -y abb-rws-mcp@0.2.0 as a stdio server in Claude Desktop, Claude Code, VS Code or Cursor.
Is abb-rws-mcp free?
Yes. abb-rws-mcp is open source, so you can use and self-host it for free.
How do I add abb-rws-mcp to Claude Code?
Run this command in your terminal: claude mcp add abb-rws-mcp -- npx -y abb-rws-mcp
What are the best alternatives to abb-rws-mcp?
The closest alternatives to abb-rws-mcp are REA, Context7, Chrome DevTools MCP, Codebase Memory and GitHub.
Where this comes from
- Description: written from the project's README.
- Install steps: from the official MCP Registry entry.


