ROS MCP Server

Created By
lpigeona year ago
The ROS MCP Server is designed to support robots in performing complex tasks and adapting effectively to various environments by providing a set of functions that transform natural language commands, entered by a user through an LLM, into ROS commands for robot control. Furthermore, by utilizing rosbridge, it is configured to operate with both ROS and ROS2 systems, and its WebSocket-based communication enables broad applicability across diverse platforms.
Overview

what is ROS MCP Server?

The ROS MCP Server is a tool designed to facilitate the control of robotic movement by providing functions for precise manipulation of linear and angular velocities, enabling robots to perform complex maneuvers and navigate various environments efficiently.

how to use ROS MCP Server?

To use the ROS MCP Server, set the IP and port to connect to rosbridge, run the rosbridge server, and then execute commands to control the robot's movement through an AI system that imports the ros_mcp_server.

key features of ROS MCP Server?

  • Sends movement commands to robots with specified linear and angular velocities.
  • Allows for multi-step motion control through a sequence of commands.
  • Compatible with ROS 1 and ROS 2 for flexible integration.

use cases of ROS MCP Server?

  1. Controlling robotic arms for precise tasks.
  2. Navigating mobile robots in complex environments.
  3. Simulating robotic movements in environments like NVIDIA Isaac Sim.

FAQ from ROS MCP Server?

  • What is the purpose of pub_twist?

pub_twist sends movement commands to the robot by setting linear and angular velocities.

  • How do I install the necessary components?

You can install the required components using the provided installation commands for uv.

  • Can I use ROS MCP Server with different versions of ROS?

Yes, it is compatible with both ROS 1 and ROS 2.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
lpigeon
Star
-
Language
-
License
-
Category

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago