MCP100 IndexMCP Server
WatchlistCommunity implementation

ROS MCP Server

by robotmcp

Reviewed October 5, 2026

MCP ServerManufacturing & Industrial

Watchlist tracking

Reviewed for relevance and future tracking value.

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow ROS distribution and robot-tool compatibility because robotics interfaces change

Reviewed · Documentation review; complete setup workflow not independently tested

Best fit

Robotics developers and operators giving AI clients controlled access to ROS 1/2 systems.

What we know

An MCP server connecting AI clients to ROS through rosbridge for inspection, telemetry and robot-control operations.

Maintenance / activity evidence

  • Observed (UTC)chore: bump version to v3.1.2 ( 392)

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

  • Installation and comprehensive security have not been independently audited.
  • Inherited from ROS/rosbridge deployment. Writes: Publish topics; Call services/actions; Change parameters.
  • Authentication not yet verified.
  • Sensitive access: Robot control, Camera/sensor data
  • Control-capable robotics integration carries physical-safety and sensitive-telemetry risk; enforce external ROS/network authorization.
Security source · repository notice ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

1,486 repository stars

Stars observed Oct 6, 2026.

No package metric used because canonical package identity was not confirmed strongly enough.

No package metric used because canonical package identity was not confirmed strongly enough.

No package metric used because canonical package identity was not confirmed strongly enough.

All limitations / Review context

Which ROS and ROS2 operations are documented and supported?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

  • Control-capable robotics integration carries physical-safety and sensitive-telemetry risk; enforce external ROS/network authorization.
  • Inherited from ROS/rosbridge deployment.
  • Live robot telemetry and images may be exposed.
  • Reviewed write actions: Publish topics; Call services/actions; Change parameters
  • Sensitive access: Robot control, Camera/sensor data
  • Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
  • A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
  • No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
  • The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
  • Exact install command
  • Authentication/authorization model
  • Canonical package identity
  • Requires running ROS and rosbridge.
  • Exact install/auth details were not fully available from top-level docs.
  • Robot control can affect physical systems.

Original activity observations

  • 2026-09-23T23:03:22Z: chore: bump version to v3.1.2 ( 392)
Technical identity
github.com/robotmcp/ros-mcp-server
Reviewed resource type
MCP Server
Repository identity
robotmcp/ros-mcp-server

Evidence & Sources

Evidence basis
Recorded source evidence
Setup runtime verification
Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed · Latest source observation