dex-isaac-mcp
Related Servers
Alternatives to dex-isaac-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceEnables AI assistants to control NVIDIA Isaac Sim by building scenes, loading assets, operating robots and humans, reading sensors, managing simulation, and creating Action Graphs.1291MIT
- AlicenseAqualityDmaintenanceEnables 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.12MIT
- AlicenseAqualityBmaintenanceEnables MCP-capable agents to see and control robots directly by listing tasks, starting and resetting episodes, observing camera feeds and robot state, and moving end effectors and grippers, including coordinating two arms. Supports LIBERO, RoboDojo, a simulator-free fake backend and remote backends over SSH or TCP, with configurable episode budgets, logs, live monitoring and frame-by-frame replay.737 PyPI5Apache 2.0
- AlicenseAqualityBmaintenanceLets agents see and drive a live 3D application session through its addon socket: viewport screenshots, turntable and multi-mode renders, scene and object inspection, arbitrary Python execution, GLB import/export and asset validation, plus rig, pose-deformation and silhouette-likeness checks. This lets an agent visually judge a 3D result instead of guessing.25MIT
- AlicenseAqualityCmaintenanceEnables an AI agent to drive Roblox Studio, including running Luau code, syncing Rojo projects, starting solo or multiplayer play tests, and retrieving logs, screenshots, and GUI information.11MIT
- 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
TDQS
Scored across 26 tools
Tools are cleanly partitioned into sim_* and train_* domains, and within sim the verbs target distinct actions (status, step, play, set_targets vs set_pose vs set_coupling). Minor overlap between sim_wave, sim_range_test, and sim_sweep is resolved by their descriptions.
All tool names use snake_case with consistent sim_ or train_ prefixes and predictable verb_noun structure, e.g. sim_set_targets, sim_get_joint_state, train_start, train_checkpoints.
26 tools is slightly above the ideal single-domain range, but the server covers two substantial subsystems: live Isaac Sim control and headless Isaac Lab training orchestration. The count is reasonable for that dual scope.
The surface covers sim lifecycle (up/down/reload, status, joint state, poses, params, camera, screenshot, experiments) and training lifecycle (start/list/status/logs/stop/checkpoints/metrics). Minor gaps include no explicit generic sim reset and no training-run cleanup/delete operation.