Check your ROS 2 environment setup and identify issues by running ros2 doctor diagnostics.
MIT
521,367 tools. Updated 2026-09-06 10:44
"ROS" matching MCP tools:
- Search for ROS 2 packages by keyword. Input a partial or full package name to retrieve matching packages from the ROS environment.MIT
- Retrieve a list of all available ROS 2 actions. Use this to discover actions your robot can perform.MIT
- Kill all running ROS 2 and Gazebo processes to reset the environment for a clean start.MIT
- Lists all currently running ROS 2 nodes to help identify active processes in the robotic system.MIT
- List all currently active ROS 2 nodes with their information to help monitor system health and troubleshoot node communication.MIT
Matching MCP Servers
- AlicenseAqualityDmaintenanceA 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.1580MIT
- AlicenseAqualityDmaintenanceEnables controlling robots in ROS environments through natural language, supporting topics, services, actions, and GUI tools.2436MIT
Matching MCP Connectors
Structure-only reference for the vanilla Ross ERP 8.0 schema, UI menu tree, and program catalog.
RSS, Atom and JSON feeds for agents: find a site's feed, read items as JSON, keyless news search.
- Monitor and debug ROS 2 systems by retrieving all active topics, including their types and publisher/subscriber counts.MIT
- Retrieve detailed information about any ROS 2 topic, including its message type, to support monitoring and debugging.MIT
- Discover all ROS 2 services in your system. Use this tool to get a complete list for monitoring and debugging.MIT
- Retrieve parameter values from a named ROS 2 node to inspect configuration and tune behavior.MIT
- Lists all available ROS 2 services. Use this to discover active services in your ROS environment.MIT
- Collect messages from a ROS 2 topic over a specified time or message count to observe data flow and diagnose problems.MIT
- Publish a message to a ROS 2 topic. Specify the topic name, message content, and optional message type to send data to running ROS 2 nodes.MIT
- Launch a ROS 2 package launch file by providing package and launch file names, with support for optional arguments.MIT
- Set a ROS 2 node parameter to a specified value by providing the node name, parameter name, and value.MIT
- Diagnose ROS 2 environment variables and setup to resolve configuration issues.MIT
- Check ROS 2 daemon and node health, optionally including diagnostics, to assess system status.MIT
- Retrieve a comprehensive list of all available ROS services to facilitate robotic movement control and system integration.Apache 2.0
- Retrieve available topics from the ROS bridge to monitor and control robotic movement across ROS and ROS2 environments.Apache 2.0
- Retrieve detailed information about any ROS 2 node by specifying its name. Get publishers, subscribers, services, and actions.MIT
- Call a ROS 2 service by specifying its name and optional request parameters in YAML format. Directly invoke services to trigger actions or retrieve data from ROS 2 nodes.MIT