Schema | ros-mcp

ros-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
list_ros_nodesA	List all currently running ROS 2 nodes and their information
list_ros_topicsA	List all ROS 2 topics with their types and publishers/subscribers
monitor_topicB	Monitor a ROS 2 topic for a specified duration. Collects messages over time.
get_topic_infoA	Get detailed information about a specific ROS 2 topic including message type
publish_to_topicB	Publish a message to a ROS 2 topic
list_ros_servicesA	List all available ROS 2 services
call_serviceC	Call a ROS 2 service with optional parameters
monitor_tf2_framesC	Monitor TF2 transform frames and their relationships
get_node_parametersA	Get parameters for a specific ROS 2 node
set_node_parameterB	Set a parameter for a ROS 2 node
get_node_connectionsA	Get all topics that a node publishes to and subscribes from
generate_ros_graphB	Generate RQT graph showing connections between nodes and topics
run_ros_launchB	Launch a ROS 2 package launch file
run_ros_nodeC	Run a ROS 2 node from a package
check_ros_system_statusB	Check overall ROS 2 system status, daemon, and node health

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/husain-zaidi/ROS-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server