Skip to main content
Glama
YidaYang

embodify-mcp

by YidaYang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to embodify-mcp

No user-submitted related servers found.

    Related Servers

    • mujoco-arm-mcp

      kevinave
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables LLM agents to control a two-joint MuJoCo robot arm through tools for moving, reading state, and resetting. It deliberately omits inverse kinematics, so the agent must infer joint angles from observations.
      MIT

    • robot-runtime

      Alonbbar6
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to safely drive a simulated Franka Panda pick-and-place cell through MCP tools, with gated motion, emergency stop, structured errors, and audit logging.
      -

    • Mobile Device MCP

      srmorete
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that lets AI agents control iOS and Android devices (tap, scroll, type, take screenshots, read UI trees, and run code). Works with multiple devices at the same time.
      102 npm
      47
      MIT
    • ghost-in-the-droid by ghost-in-the-droid

      ghost-in-the-droidofficial

      ghost-in-the-droid
      A
      license
      B
      quality
      A
      maintenance
      Give any LLM agent a real Android or iPhone. 62 MCP tools: tap, swipe, type, screenshot, screen-tree reading, app launch, camera, TTS, crash reports, batched execution. Android via ADB, iPhone via WebDriverAgent, on-device inference, Docker+KVM emulators. Works with Claude Code, Cursor, LangChain, LlamaIndex, and any MCP client. MIT.
      66
      94 PyPI
      370
      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 7 tools

    Disambiguation4/5

    The tools map cleanly to distinct phases of the simulation loop: start (reset_task), observe (observe), act (move_relative, set_gripper), end (stop_episode), and introspect (get_session_info, list_tasks). There is minor overlap in that observe and get_session_info both return robot state, but their descriptions clearly separate their roles (images during a run vs. run metadata callable anytime).

    Naming Consistency4/5

    Six of seven tools follow a verb_noun pattern (reset_task, move_relative, set_gripper, stop_episode, get_session_info, list_tasks). observe is a bare verb without a noun, a minor deviation, but overall the naming is predictable and readable.

    Tool Count5/5

    Seven tools exactly cover the full episode lifecycle without redundancy or bloat. Every tool earns its place: reset, observe, two action primitives, stop, session info, and task listing are all necessary for the stated purpose.

    Completeness4/5

    The surface covers task discovery, episode reset, observation, action, episode termination, and session introspection, which is the core loop. A minor gap is the lack of an explicit reward/success query, though stop_episode artifacts (summary, events) likely provide results for agents able to read them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources