ROS MCP Server

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL

https://heyclau.de/entry/mcp/ros-mcp-server

Source URLs

https://raw.githubusercontent.com/robotmcp/ros-mcp-server/main/docs/install/installation.md, https://github.com/robotmcp/ros-mcp-server

Brand

ROS MCP Server

Brand domain

github.com

Safety notes

ROS MCP Server can expose robot observation and control surfaces to an AI client, including topic publishing, topic subscription, service calls, action calls, parameter updates, sensor reads, and robot state inspection., Treat every topic, service, action, and parameter exposed through rosbridge as potentially capable of moving hardware, changing robot behavior, altering safety limits, or interrupting active tasks., Validate workflows in simulation or with the robot immobilized before allowing commands on mobile bases, manipulators, drones, industrial equipment, or other physical systems., Keep an operator, emergency stop, physical safety perimeter, and robot-specific lockout procedures in place for live hardware., Restrict rosbridge to trusted networks, approved clients, and the minimum reachable robot namespace needed for the task., Review generated commands before execution when using custom message types, services, actions, or parameters that the model has inferred from live ROS metadata.

Privacy notes

ROS topics and services can expose camera frames, sensor data, maps, robot poses, facility layouts, task names, device identifiers, hostnames, IP addresses, and operational telemetry., Images, logs, maps, and robot state returned to the MCP client may also be sent to the model provider or stored by the MCP client, terminal, or chat application., rosbridge traffic crosses the local network or VPN; protect robot networks from untrusted clients and avoid exposing rosbridge directly to the public internet., Review launch files, client configs, environment variables, and connection prompts for credentials, robot addresses, VPN details, or internal network names before sharing transcripts.

Author

robotmcp

Submitted by

oktofeesh1

Claim status

unclaimed

Last verified

2026-06-06

• ROS topics and services can expose camera frames, sensor data, maps, robot poses, facility layouts, task names, device identifiers, hostnames, IP addresses, and operational telemetry.
• Images, logs, maps, and robot state returned to the MCP client may also be sent to the model provider or stored by the MCP client, terminal, or chat application.
• rosbridge traffic crosses the local network or VPN; protect robot networks from untrusted clients and avoid exposing rosbridge directly to the public internet.
• Review launch files, client configs, environment variables, and connection prompts for credentials, robot addresses, VPN details, or internal network names before sharing transcripts.

• Python 3.10 or newer on the machine running the MCP client.
• A ROS or ROS 2 robot, simulator, or development machine with rosbridge available.
• Network access from the MCP server machine to the rosbridge WebSocket endpoint.
• Familiarity with the robot's topics, services, actions, parameters, frames, and safety limits.
• A simulation, test bench, or supervised robot environment for validating prompts before live operation.

Show that ROS MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

[![Listed on HeyClaude](https://heyclau.de/badge/mcp/ros-mcp-server.svg)](https://heyclau.de/entry/mcp/ros-mcp-server)

ROS MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field	ROS MCP Server MCP server that connects Claude and other MCP clients to ROS and ROS 2 robots through rosbridge for topic, service, action, parameter, sensor, and robot state workflows. Open dossier	AI Game Developer Unity MCP Server Unity MCP server, plugin, CLI, and skill generator for controlling Unity Editor and runtime projects from MCP clients through built-in game-dev tools. Open dossier	HttpRunner UIXT MCP Server MCP server from HttpRunner that exposes UIXT device and browser automation tools for Android, iOS, Harmony, and Web testing through the `hrp mcp-server` command. Open dossier	macOS Automator MCP MCP server for running AppleScript and JavaScript for Automation on macOS, with a searchable knowledge base of automation recipes for apps, files, browsers, system settings, Terminal, and productivity workflows. Open dossier
Next steps	Open dossierCopy installCopy configAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing	Open dossierCopy installCopy configAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing	Open dossierCopy installCopy configAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing	Open dossierCopy installCopy configAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Trust	Review first	Review first	Review first	Review first
Review status	Not reviewed	Not reviewed	Not reviewed	Not reviewed
Package trust	Package not verified	Package not verified	Package not verified	Package not verified
Source provenance	Source-backed	Source-backed	Source-backed	Source-backed
Submitter	oktofeesh1	oktofeesh1	oktofeesh1	oktofeesh1
Install risk	Review first	Review first	Review first	Review first
Notes	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓
Brand	—	AI Game Developer	HttpRunner	—
Category	mcp	mcp	mcp	mcp
Source	Source-backed	Source-backed	Source-backed	Source-backed
Author	robotmcp	Ivan Murzak	debugtalk	Peter Steinberger
Added	2026-06-06	2026-06-06	2026-06-06	2026-06-06
Platforms	Claude CodeCodexCursorClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop
Harness	Claude CodeCodexCursorClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop
Source repo	—	—	—	—
Safety notes	✓ROS MCP Server can expose robot observation and control surfaces to an AI client, including topic publishing, topic subscription, service calls, action calls, parameter updates, sensor reads, and robot state inspection. Treat every topic, service, action, and parameter exposed through rosbridge as potentially capable of moving hardware, changing robot behavior, altering safety limits, or interrupting active tasks. Validate workflows in simulation or with the robot immobilized before allowing commands on mobile bases, manipulators, drones, industrial equipment, or other physical systems. Keep an operator, emergency stop, physical safety perimeter, and robot-specific lockout procedures in place for live hardware. Restrict rosbridge to trusted networks, approved clients, and the minimum reachable robot namespace needed for the task. Review generated commands before execution when using custom message types, services, actions, or parameters that the model has inferred from live ROS metadata.	✓AI Game Developer can create, move, copy, modify, and delete Unity assets, scenes, GameObjects, components, scripts, packages, and generated project files. Tools include dynamic C# script execution, C# reflection method lookup and calls, package installation/removal, Unity test execution, editor state changes, play mode control, screenshots, and profiler access. The MCP server supports streamable HTTP and stdio; HTTP deployments should require a bearer token and stay bound to trusted interfaces. Server variables include optional authorization and webhook settings; webhook endpoints can receive tool, prompt, resource, connection, and authorization events. Unity runtime connections can expose compiled game state or in-game behavior to an MCP client, not just editor-only project data. Use source control, backups, tool filtering, and explicit review before allowing destructive tools such as asset deletion, package removal, script execution, or reflection calls.	✓HttpRunner UIXT MCP Server can control real devices and browsers through taps, swipes, text input, hardware buttons, selectors, OCR, CV, and AI action tools. App tools can launch, terminate, cold launch, install, uninstall, clear data, and inspect foreground apps on connected devices. Screen tools can capture screenshots, screen recordings, screen size, and UI hierarchy/source data. Media and utility tools can modify test-device albums, close popups, wait randomly, and interact with system UI state. Simulated gesture options and anti-risk-style behavior should be used only in authorized test automation environments. Require human review before running actions against logged-in accounts, payment flows, device settings, production apps, or customer data.	✓macOS Automator MCP executes AppleScript or JavaScript for Automation through `osascript`, either from inline script content, an absolute script path, or a knowledge-base script ID. AppleScript and JXA can control local applications, read and write files, run shell commands through scripting additions, manipulate browser tabs, send keystrokes, change settings, and trigger app-specific actions depending on macOS permissions. Do not grant broad Automation or Accessibility permissions to the host process unless you trust the MCP client, prompts, and scripts it will run. Review generated scripts before execution, use short timeouts for untrusted automations, and avoid running scripts against Mail, Messages, Contacts, Calendar, browsers, password managers, terminals, or cloud-sync folders without explicit approval. Knowledge-base scripts and custom local knowledge-base overrides can change the behavior of reusable script IDs; review local overrides before relying on them. Use separate macOS user accounts or test machines when experimenting with destructive file, shell, browser, or system-setting automation.
Privacy notes	✓ROS topics and services can expose camera frames, sensor data, maps, robot poses, facility layouts, task names, device identifiers, hostnames, IP addresses, and operational telemetry. Images, logs, maps, and robot state returned to the MCP client may also be sent to the model provider or stored by the MCP client, terminal, or chat application. rosbridge traffic crosses the local network or VPN; protect robot networks from untrusted clients and avoid exposing rosbridge directly to the public internet. Review launch files, client configs, environment variables, and connection prompts for credentials, robot addresses, VPN details, or internal network names before sharing transcripts.	✓Tool calls may expose Unity project paths, asset names, scene hierarchy, serialized object data, scripts, logs, screenshots, profiler metrics, test output, package metadata, and runtime state. MCP config files and Unity plugin config can contain server URLs, connection modes, bearer tokens, authorization settings, enabled tool IDs, and cloud or local endpoint details. Optional webhooks can receive tool, prompt, resource, connection, authorization, and token-bearing request data. Screenshots from Game View, Scene View, cameras, or isolated GameObjects may include proprietary artwork, level design, UI, debug overlays, or unreleased game content. Generated skills and AI-client configuration files can reveal available tools, project structure, installed packages, and local workflow assumptions.	✓Screenshots, screen recordings, UI hierarchy, package names, foreground app names, OCR text, selector data, and logs can expose sensitive app or account state. Connected device identifiers, serial numbers, app package names, browser pages, and test artifacts may be visible to the MCP client. Input and paste actions can expose credentials, one-time codes, chat text, forms, or clipboard-like data if used on personal sessions. Test reports, MCP responses, and debugging logs may retain captured UI state after the session ends. Keep test devices resettable, avoid personal accounts, and isolate artifacts produced by automated UI runs.	✓Scripts can expose local file paths, file contents, clipboard data, browser URLs and page data, email subjects, contacts, calendar events, messages, app state, system settings, shell output, and account-specific metadata. Error responses and optional debugging settings can include attempted script content, script paths, substitution logs, stderr, and execution details. The local knowledge base defaults to `~/.macos-automator/knowledge_base` when configured and may contain private automation recipes or paths. MCP clients, model providers, terminal history, and application logs may retain script inputs and outputs, including data read from local apps.
Prerequisites	Python 3.10 or newer on the machine running the MCP client. A ROS or ROS 2 robot, simulator, or development machine with rosbridge available. Network access from the MCP server machine to the rosbridge WebSocket endpoint. Familiarity with the robot's topics, services, actions, parameters, frames, and safety limits.	Unity project using Unity 2022.3 or newer for the current package metadata. Unity Hub or a local Unity Editor installation. Node.js 20.19 or newer, or Node.js 22.12 or newer, for `unity-mcp-cli`. An MCP client such as Claude Code, Claude Desktop, Codex, Cursor, Gemini CLI, GitHub Copilot, Cline, or another supported client.	Go 1.23 or newer for building the current v5 CLI from source. A test Android, iOS, Harmony, or browser automation environment configured for HttpRunner UIXT. A trusted MCP client that can launch local stdio servers. Review of ADB, go-ios, WebDriver, OCR, computer-vision, and AI-action dependencies required by your target platform.	macOS on the machine running the MCP server. Node.js 24 or newer for the published npm package. Automation permissions for the terminal, editor, or app that launches the MCP server. Accessibility permissions when scripts need UI scripting, clicks, keystrokes, or System Events access.
Install	uvx ros-mcp --transport=stdio Copy install	npm install -g unity-mcp-cli && unity-mcp-cli install-plugin ./MyUnityProject Copy install	git clone https://github.com/httprunner/httprunner.git && cd httprunner && go build -o hrp ./cmd/cli Copy install	npx -y --package @steipete/macos-automator-mcp macos-automator-mcp Copy install
Config	{ "mcpServers": { "ros-mcp": { "command": "uvx", "args": [ "ros-mcp", "--transport=stdio" ], "type": "stdio" } } } Copy config	Manual-only setup: npm install -g unity-mcp-cli unity-mcp-cli install-plugin ./MyUnityProject unity-mcp-cli open ./MyUnityProject Copy config	{ "mcpServers": { "httprunner-uixt": { "command": "hrp", "args": [ "mcp-server" ], "type": "stdio" } } } Copy config	{ "mcpServers": { "macos_automator": { "command": "npx", "args": [ "-y", "--package", "@steipete/macos-automator-mcp", "macos-automator-mcp" ], "type": "stdio" } } } Copy config
Citations	Source repositorygithub.com 2026-07-21T07:17:01+00:00 Documentationraw.githubusercontent.com Submitted by oktofeesh12026-06-06 Source methodology →	Source repositorygithub.com 2026-07-21T07:17:01+00:00 Documentationraw.githubusercontent.com Submitted by oktofeesh12026-06-06 Source methodology →	Source repositorygithub.com 2026-07-21T07:17:01+00:00 Documentationraw.githubusercontent.com Submitted by oktofeesh12026-06-06 Source methodology →	Source repositorygithub.com 2026-07-21T07:17:01+00:00 Documentationraw.githubusercontent.com Submitted by oktofeesh12026-06-06 Source methodology →
Claim	Unclaimed	Unclaimed	Unclaimed	Unclaimed

Source-backed guides for putting this to work.