F
licenseNot graded
qualityD
maintenanceControls toio robot cubes via natural language through BLE, enabling movement, LED control, and sound playback from MCP-compatible clients like Claude Desktop.
1
-
sphero-rvr-mcp
by jsperson
Related Servers
Alternatives to sphero-rvr-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to control a littleBits R2-D2 robot over Bluetooth Low Energy by calling tools to drive and play sounds.-
- AlicenseNot gradedqualityDmaintenanceEnables AI models to monitor and control Kachaka robots via MCP, including navigation, shelf operations, and sensor data access.1Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables natural language control of an esieabot robot (motors, servo, camera) through Claude Desktop or MCP Inspector.-
- AlicenseDqualityBmaintenanceBridges MCP-compatible AI assistants with the Stack-chan robot, enabling speech, listening, vision, movement, and facial expressions through MCP tool calls.1476MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to control Home Assistant smart home devices via MCP, with zero external dependencies. Supports calling services, getting states, and looking up service parameters.17 npmMIT
TDQS
C2.7/5.0
Scored across 55 tools
Disambiguation4/5
Most tools target distinct actions or sensors, but there is some overlap: multiple battery getters (status, voltage, voltage_state, thresholds) and get_sensor_data could be seen as a catch-all that duplicates specific getters. The test tools and connect_simple/connect add minor confusion, but descriptions generally clarify boundaries.
Naming Consistency4/5
The majority of tools use a consistent verb_noun pattern (get_*, set_*, start_*, stop_*, drive_*). However, there are deviations like test_immediate_return, test_slow_return, connect_simple, emergency_stop, clear_emergency_stop, and turn_leds_off which break the pattern slightly.
Tool Count2/5
With 55 tools, the server is well beyond the typical 3-15 range and even exceeds the 25+ threshold. The surface is bloated with redundant test utilities and multiple specialized getters that could be consolidated, making it overwhelming for agents.
Completeness4/5
The toolset covers core robot operations: connection, driving, LEDs, sensors, IR, battery, safety, and system info. Notable gaps include a direct position getter (only reset_locator and encoder counts) and no gyroscope/accelerometer readings, but the domain is largely covered.
Maintenance
ActivityInactive
ResponsivenessNo issues