mujoco-mcp
Related Servers
Alternatives to mujoco-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceExposes a local simulated two-arm robot to TUI agents through stateful, serialized MCP tools that start trials, return camera images and joint state, jog the arm or move joints within bounded limits, and finish runs with scored metrics and native Inspect log paths. Agents can therefore drive and record robotic manipulation rollouts in Chrome-visible MuJoCo physics without any robot hardware or policy weights.1AGPL 3.0
- FlicenseNot gradedqualityBmaintenanceMCP server exposing UniRoboSim evidence, simulation state, camera images, and optional explicit control of owned simulation sessions.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to connect to running Abaqus/CAE windows over multi-port TCP sockets, discover and switch sessions, and execute Python, model, job, ODB, and viewport operations targeted by session_id.MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseNot gradedqualityAmaintenanceConnects MCP clients such as Claude, Cursor, and VS Code to an OpenCode server's headless API, enabling users to ask questions, delegate and run coding tasks, monitor background jobs, answer prompts and permission requests, and review resulting changes across multiple projects. Sessions accept absolute server-side project directories, support both blocking and asynchronous workflows, and expose persisted job records for recovering or cancelling work.24,321 npmMIT
- AlicenseAqualityBmaintenanceLets AI agents drive a live, persistent Isaac Sim session: load any articulated robot from a USD plus JSON config, set normalized joint targets and named poses, tune gains and couplings live, run joint range tests, and capture screenshots. It also launches and monitors detached Isaac Lab training runs, with Kit kept up between calls so each experiment costs a frame instead of a full relaunch.2630 PyPIMIT
TDQS
Scored across 17 tools
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.
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.
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.
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.