ROS MCP Server

MCP server by robotmcp

Connect LLMs to ROS and ROS 2 robots to work with topics, services, actions and parameters through rosbridge.

Runs locally (Runs on your machine: its page has the install command)Runs with uvx

Install ROS MCP Server

Runs on your machine. Your client starts it with this command:

uvx ros-mcp --transport=stdio

Needs uv (Python) on your computer. The setup steps below show where the command goes in each client.

Share this server

Opens this page, with the install command and setup steps.

mcp.tc/i/ros

About

ROS MCP Server lets an AI assistant control and observe robots running ROS 1 or ROS 2. It can publish and subscribe to topics, call services and actions, set parameters, read sensor data and monitor robot state. It helps the model discover available topics, services and actions, including custom types, and use them with the right syntax.

It runs locally over stdio as the PyPI package ros-mcp, started with uvx. It talks to the robot through a rosbridge WebSocket node, so no changes to existing robot code are needed. No sign-in or API key is required. It works with MCP clients such as Claude Code, Claude Desktop, Cursor, Codex CLI and Gemini CLI.

What you can do

  • Publish and subscribe to ROS topics
  • Call ROS services and actions
  • Read and set robot parameters
  • Read sensor data and monitor robot state
  • Discover topics, services and custom message types
  • Works with ROS 1 and ROS 2 distributions

Tools

Local servers list their tools once they’re running, and this one doesn’t publish its list in advance. Your client shows them after you add it.

Example prompts

  • List all topics available on my robot and show their message types.

  • Subscribe to the lidar topic and tell me if anything is close to the robot.

  • Call the gripper service and check whether the end effector responds correctly.

  • Read the current navigation parameters and summarize them.

Set up

Every client starts ROS MCP Server on your machine with the same command. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport stdio ros -- uvx ros-mcp --transport=stdio
  1. Start Claude Code and type /mcp. ros should show as connected.

Add --scope user to make it available in every project.

Claude Desktop

  1. Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:
claude_desktop_config.json
{
  "mcpServers": {
    "ros": {
      "command": "uvx",
      "args": [
        "ros-mcp",
        "--transport=stdio"
      ]
    }
  }
}
  1. Save the file and restart Claude Desktop.

Needs uv (Python) on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "ros": {
      "command": "uvx",
      "args": [
        "ros-mcp",
        "--transport=stdio"
      ]
    }
  }
}

Needs uv (Python) on your computer.

VS Code

Or from a terminal:

code --add-mcp '{"name":"ros","type":"stdio","command":"uvx","args":["ros-mcp","--transport=stdio"]}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "ros": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "ros-mcp",
        "--transport=stdio"
      ]
    }
  }
}

Needs uv (Python) on your computer.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "ros": {
      "command": "uvx",
      "args": [
        "ros-mcp",
        "--transport=stdio"
      ]
    }
  }
}
  1. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add ros -- uvx ros-mcp --transport=stdio

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.ros]
command = "uvx"
args = ["ros-mcp", "--transport=stdio"]

Needs uv (Python) on your computer.

Gemini CLI

gemini mcp add ros uvx -- ros-mcp --transport=stdio

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

{
  "mcpServers": {
    "ros": {
      "command": "uvx",
      "args": [
        "ros-mcp",
        "--transport=stdio"
      ]
    }
  }
}

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs uv (Python) on your computer.

FAQ

Can I paste mcp.tc/i/ros into my MCP client?

No. ROS MCP Server runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is uvx ros-mcp --transport=stdio.

Does ROS MCP Server need an API key?

No. It doesn’t declare any keys or environment variables. It runs with your user account’s permissions, so check what its tools can reach.

Is ROS MCP Server a remote or a local server?

Local. Your client starts it as a process on your computer with uvx ros-mcp --transport=stdio, which needs uv (Python).

What can ROS MCP Server do?

You can publish and subscribe to ROS topics, call ROS services and actions and read and set robot parameters.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Who wrote this page?

mcp.tc’s robot read ROS MCP Server’s public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

Embed

Show ROS MCP Server in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work

README badge

Badge preview, lightBadge preview, dark
Markdown
[![ROS MCP Server on mcp.tc](https://mcp.tc/i/ros/badge.svg)](https://mcp.tc/i/ros)
HTML
<a href="https://mcp.tc/i/ros"><img src="https://mcp.tc/i/ros/badge.svg" alt="ROS MCP Server on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/ros.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/ros" title="ROS MCP Server on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/ros.json

What each field means

mcp.tc isn’t affiliated with robotmcp. This page was built from ROS MCP Server’s public metadata, last checked on 3 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.