wise-vision/mcp_server_ros_2
If you are the rightful owner of mcp_server_ros_2 and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.
WiseVision ROS2 MCP Server is a Python server implementing the Model Context Protocol (MCP) for ROS2, facilitating communication and data handling in ROS2 environments.
WiseVision ROS2 MCP Server
A Python implementation of the Model Context Protocol (MCP) for ROS2. This server enables AI tooling to connect with ROS2 nodes, topics, and services using the MCP standard over stdio. It is designed to be the easiest ROS2 server to configure in the world.
🎯 Why Choose This MCP Server?
Save hours of development time with native AI integration for your ROS2 projects:
- ⚡ 1-minute setup - World's easiest ROS2 MCP configuration
- 0️⃣ Zero-friction setup - stdio transport, no brokers, no webserver.
- 🔌 Auto-discovery - a built-in “list interfaces” tool dynamically enumerates available topics and services together with their message/service definitions (fields, types, schema) — so the client always knows exactly what data can be published or called.
- 🤖 AI-powered debugging - Let AI help you troubleshoot ROS2 issues in real-time
- 📊 Smart data analysis - Query your robot's sensor data using natural language
- 🚀 Boost productivity - Control robots, analyze logs, and debug issues through AI chat
- 💡 No ROS2 expertise required - AI translates your requests into proper ROS2 commands
Perfect for: Robotics developers, researchers, students, and anyone working with ROS2 who wants to leverage AI for faster development and debugging.
🚀 Enjoying this project?
You’re welcome to try the Pro version with extra features and priority support.
👉 Get Pro here
🌍 Real-world examples:
✨ Features
- List available topics
- List available services
- Call service
- Get messages from WiseVision Data Black Box (influxDB alternative to Rosbag2)
- Subscribe topic to get messages
- Publish message on topic
- Echo message on topic
- Get fields from message type
Note: To call service with custom service source it before start server.
⚙️ Installation
Follow the for step-by-step instructions:
🔧 ROS 2 Tools
📋 Topics
| Tool | Description | Inputs | Outputs |
|---|---|---|---|
ros2_topic_list | Returns list of available topics | – | topic_name (string): Topic name topic_type (string): Message type |
ros2_topic_subscribe | Subscribes to a ROS 2 topic and collects messages for a duration or message limit | topic_name (string) duration (float) message_limit (int) (defaults: first msg, 5s) | messages count duration |
ros2_get_messages | Retrieves past messages from a topic (data black box) | topic_name (string) message_type (string) number_of_msg (int) time_start (str) time_end (str) | timestamps messages |
ros2_get_message_fields | Gets field names and types for a message type | message_type (string) | Field names + types |
ros2_topic_publish | Publishes message to a topic | topic_name (string) message_type (string) data (dict) | status |
🛠 Services
| Tool | Description | Inputs | Outputs |
|---|---|---|---|
ros2_service_list | Returns list of available services | – | service_name (string) service_type (string) request_fields (array) |
ros2_service_call | Calls a ROS 2 service | service_name (string) service_type (string) fields (array) force_call (bool, default: false) | result (string) error (string, if any) |
🐞 Debugging
Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the MCP Inspector.
You can launch the MCP Inspector via npm with this command:
npx @modelcontextprotocol/inspector uv --directory /path/to/mcp_server_ros2 run mcp_ros_2_server
Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.
