Skip to main content
Glama
Lecoeurdelest

mujoco-mcp

by Lecoeurdelest
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to mujoco-mcp

No user-submitted related servers found.

    Related Servers

    • UniRoboSim MCP

      GitHofee
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server exposing UniRoboSim evidence, simulation state, camera images, and optional explicit control of owned simulation sessions.
      -

    • playtest-mcp

      kevinnie2003
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to run autonomous game playtesting, evaluate the agent against seeded bugs, list bug flags, and interactively reset, step, and view game sessions.
      MIT

    • Cascadeur MCP

      gprethesh
      A
      license
      A
      quality
      C
      maintenance
      Enables AI clients to control Cascadeur locally for scene and rig inspection, body and finger animation, keyframes, physics actions, camera control, PNG previews, and FBX import/export via stdio MCP.
      36
      1
      MIT

    • Chip-AgentX MCP Server

      levitation-well
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables external clients to spawn, control, observe, and terminate isolated AI coding agent sessions over MCP via stdio or Streamable HTTP, with scoped chip datasheet knowledge-base retrieval.
      -
    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 17 tools

    Disambiguation5/5

    Each tool maps to a distinct responsibility: session lifecycle, model inspection, stepping, state access, snapshots, viewer control, contact measurement, experiment configuration, and provenance. Even the paired tools like step/step_guarded and get_state/get_snapshot are clearly separated by their exact purpose and behavior.

    Naming Consistency5/5

    All tools consistently use the mujoco_ prefix with a clear snake_case verb_noun pattern (load_model, get_state, close_session, set_running, restore_snapshot). There are no mixed naming conventions or vague generic verbs.

    Tool Count4/5

    17 tools is slightly above the typical well-scoped range, but the count is justified by the breadth of the domain: session management, physics stepping, state access, snapshot handling, viewer control, and experiment configuration. A few tools could potentially be consolidated, but none feel redundant.

    Completeness5/5

    The tool set covers the full simulation lifecycle: load, inspect, step, read/write state, reset, snapshot/restore, run experiments, measure contacts, and close sessions. It also includes reproducibility-oriented tools like provenance and snapshots, so agents can execute and evidence a complete MuJoCo workflow without obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources