"ROS" matching MCP servers:

A Model Context Protocol (MCP) server for ROS 2 that enables GitHub Copilot and other AI agents to interact with ROS 2 systems. This server provides tools for monitoring, debugging, and managing ROS 2 nodes, topics, services, and TF2 frames.

Enables controlling robots in ROS environments through natural language, supporting topics, services, actions, and GUI tools.

A Model Context Protocol server for ROS 2, enabling AI assistants to introspect and interact with ROS 2 systems.

Enables large language models to interact with ROS robots seamlessly, allowing natural language control, real-time sensor monitoring, and autonomous task execution without modifying existing robot code.

Provides static analysis of ROS 2 workspaces, enabling inspection of packages, dependencies, interfaces, launch files, and robot descriptions without running ROS 2.

A read-only MCP server that enables LLMs to inspect and analyze ROS 2 systems through natural language, covering nodes, topics, parameters, actions, rates, QoS, and environment health. It can run without ROS 2 installed and safely surfaces runtime system state for diagnosis.

Enables natural language control and monitoring of ROS 2 robots through standardized MCP tools, with a deterministic safety layer and automatic capability discovery.

A Python-based server that enables AI assistants to control robots by integrating the Model Context Protocol (MCP) with ROS 2, allowing for natural language commands that translate into robot movement via the /cmd\_vel topic.

Enables AI agents to analyze ROS2 log files across multiple nodes by merging them into a unified timeline and providing smart query tools, without requiring ROS2 installation.

An MCP server for ROS 2 development that enables controlled creation of workspaces, packages, nodes, launch files, and tests within a sandboxed directory, with secure filesystem boundaries.

Connects AI agents like Claude to live ROS2 robots, enabling natural language interaction for diagnostics, parameter tuning, and control with safety sandboxing.

rm_mcp bridges ROS Noetic and ROS 2 with Model Context Protocol, providing AI Agents with structured 'eyes' (state & system inspection) and 'hands' (controller actuation, signal injection, rosbag recording, and automated PID response analysis) for robotics debugging.

A read-only MCP server for bounded semantic inspection of ROS 2 perception systems, enabling discovery and metadata extraction from sensors such as cameras, depth sensors, and LiDARs without device configuration or actuation.

This MCP server enables inspecting ROS 2 manipulators, computing kinematics, planning motion, and managing primitive MoveIt planning-scene objects via a typed API, with no physical execution support.

Enables agents to inspect and analyze ROS recordings through MCP tools and resources, including topic indexing, frame/point-cloud/depth sampling, IMU/odometry series, calibration, and exportable clips, previews, and reports. It provides bounded queries and materialization of analysis artifacts without requiring a ROS installation.

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.

This MCP server gives LLM agents eyes - the ability to see and understand their physical environment through an Intel RealSense depth camera.

Enables AI tools to interact with ROS2 robotics systems through natural language commands. Supports topic publishing/subscribing, service calls, message analysis, and auto-discovery of ROS2 interfaces for debugging and controlling robots.

Enables natural language command control of robots via ROS2, with a web portal for real-time visualization and interaction.

MCP server for AI agents to inspect and control ROS2 graphs, enabling topic listing, node info, service calls, parameter management, and pub/echo without manual ROS2 CLI usage.