Skip to main content
Glama
joeynyc

microduck-mcp

by joeynyc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to microduck-mcp

No user-submitted related servers found.

    Related Servers

    • duck-mcp

      aj-dev-smith
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to control a simulated Pollen Robotics Microduck through MCP tools for movement, tricks, pushing, camera views, and state inspection.
      8
      2
      Apache 2.0

    • Unitree Go2 MCP Server

      sallu-786
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLM agents to control and monitor a Unitree Go2 robot through MCP tools, including live telemetry, navigation, camera feeds, and waypoint missions.
      Apache 2.0

    • omni-kit-mcp

      inbarajaldrin
      A
      license
      A
      quality
      B
      maintenance
      Enables driving Omniverse Kit apps (Isaac Sim, Isaac Lab) over MCP, allowing agents to control simulations, run Python, and call namespace-scoped tools via a single bridge.
      1
      1
      MIT

    • unitree-sdk2-mcp

      ros-claw
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for controlling Unitree robots via DDS protocol, supporting G1, Go2, H1, H2, B2, A2, R1 and more. Enables LLM agents to command robots with high-level actions and safety guards.
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 8 tools

    Disambiguation4/5

    The status tools (version, health, updates, monitor) overlap somewhat in being read-only system queries, but their descriptions clearly partition them into identity, health, software releases, and live robot state. Motion tools (stop, walk, behavior) and camera are unambiguous.

    Naming Consistency4/5

    All tools share a consistent duck_ prefix and the names are short, readable, and predictable. The mix of noun-like names (duck_camera, duck_health) and imperative verbs (duck_stop, duck_walk) is a minor deviation rather than a chaotic convention.

    Tool Count5/5

    Eight tools is well-scoped for a robot observation and control server: four read-only status/observation tools, three motion/behavior tools, and one emergency stop. Each tool has a clear purpose and none feel redundant.

    Completeness5/5

    The tool set covers the full intended workflow: inspect health and state, get a visual feed, command locomotion and behaviors, and stop in an emergency. The deliberate exclusion of update installation/rollback is documented and does not leave an operational gap for normal robot use.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources