Skip to main content
Glama
aryanmangal769

embodied-mcp

by aryanmangal769
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to embodied-mcp

No user-submitted related servers found.

    Related Servers

    • ROS MCP

      Yutarop
      A
      license
      A
      quality
      D
      maintenance
      Enables controlling robots in ROS environments through natural language, supporting topics, services, actions, and GUI tools.
      24
      36
      MIT

    • genesis-mcp-robotics

      1douya1
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables LLM agents to control robot simulations (grasping, pouring) in the Genesis physics simulator through persistent sessions, allowing multi-turn interaction with the same scene.
      -

    • operandi-mcp

      ArchieAngelBeWithUs-prog
      A
      license
      A
      quality
      C
      maintenance
      Enables agents to identify appliances and retrieve grounded, robot-executable operation packages, reducing hallucinations from 24% to nearly 0%.
      4
      Academic Free v1.1

    • CarlaMCP

      codebymov
      A
      license
      A
      quality
      D
      maintenance
      Enables natural language-driven creation and execution of autonomous-vehicle scenarios in the CARLA simulator, with validated primitives and replay support.
      7
      1
      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

    Disambiguation5/5

    Each tool serves a distinct function: perception (get_view), grounding (ground), navigation (drive_to, stop), numerical parsing (parse_numerical), counting (count_in_view), finalizing counts (commit_count), and object publication (publish_object). There is no overlap or ambiguous boundaries between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_phrase pattern with snake_case (e.g., get_view, drive_to, commit_count). The verbs are imperative and descriptive, making the intent of each tool predictable from its name alone.

    Tool Count5/5

    With 8 tools, the server is well-scoped for embodied navigation and counting tasks. Each tool covers a necessary step in the workflow without redundancy or excessive granularity, fitting within the ideal 3-15 tool range.

    Completeness5/5

    The tool surface fully covers the lifecycle of the domain: perceiving the environment, grounding references, moving, stopping, parsing questions, counting from multiple views, committing aggregated results, and publishing object markers. There are no obvious gaps or dead ends for the intended tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources