Categories › Software Development › Hardware, IoT, embedded & 3D printing
Specs of commercially available robots, each figure citing its source document.
Remote server: your requests and data go to api.droid.monster. Claude Code: claude mcp add --transport http droid-monster-specs https://api.droid.monster/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
search_robots — Find robots by name, maker or kind of robot. Returns each robot's reference for the other tools, and how many specs we hold for it.find_robots — Filter robots by published figures, e.g. payload at least 20 kg and reach at least 1300 mm, optionally within a category or maker, sorted byget_robot — Everything we hold on one robot: each spec in its canonical unit, the value as the maker published it, and the document it came from.compare_robots — Two to four robots side by side, one row per figure any of them publishes. A robot that doesn't publish a figure shows null (unknown).list_attributes — The figures we record (the keys find_robots filters on), with canonical units, allowed values, and how many robots publish each. Give a catelookup_error_code — What a robot maker's error code means: its title, the likely causes the maker lists, and a link to the page of the maker's document. Currentfind_parts — Spare parts that fit a robot, each with the part number, the document that says it fits (the maker's catalogue or manual, or an authorised sfind_mcp_servers — Other MCP servers that work with robots -- driving ROS robots and arms, simulators, robot data, buying or renting robots -- from droid.monstNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.