Isaacsim MCP Server

If you already use Isaacsim, the isaacsim mcp server is the piece that lets your assistant work with it directly. Connect any MCP-compatible IDE (Cursor, VS Code, Claude Code, Windsurf, JetBrains) to a running Isaac Sim instance and control it with plain-English prompts -- create robots, build scenes, run simulations, and debug physics all from your.

What the server does

• 42 tools — across 9 categories -- scene, objects, lighting, robots, sensors, materials, assets, simulation, graphs
• 107+ robots — auto-discovered from the Isaac Sim asset library (Franka, UR, Unitree, Boston Dynamics, and more)
• Step-and-observe — debugging -- step the simulation and inspect prim positions, joint states, and physics in one call
• Hot-reload — -- iterate on Python controllers without restarting Isaac Sim
• Multi-instance — -- run multiple Isaac Sim sessions side by side on different ports
• Built for Isaac Sim 5.1.0 with a modular adapter layer for version isolation

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Category — Count
• Scene — 7
• Objects — 4
• Lighting — 2
• Robots — 6
• Sensors — 4
• Materials — 2
• Assets — 4
• Graphs — 2
• Simulation — 11
• Requirements — The Requirements tool exposed by this server

Installation

Installation goes through your MCP client rather than a global install: point it at isaacsim-mcp-server on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Credentials and setup notes

Configuration is passed through the environment: ISAAC_MCP_PORT, BEAVER3D_MODEL, ARK_API_KEY, NVIDIA_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

| Requirement | Version | |-------------|---------| | NVIDIA Isaac Sim | 5.1.0 | | Python | 3.10+ | | uv | latest (for source install) | | Platform | Linux (Ubuntu 22.04+) | > [!IMPORTANT] > Currently only Linux is supported. Windows support is planned. > macOS is not supported because NVIDIA Isaac Sim does not run on macOS. > [!NOTE] > We are welcoming contributions to support other

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Isaacsim's toolset — Category, Scene, Objects and 8 more — is a fair guide to whether it matches your workflow. It is maintained by whats2000; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Isaacsim.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.