isaacsim-mcp
MCP server that lets MCP Client execute Python code inside a running NVIDIA Isaac Sim instance and read its console output.
It uses the Isaac Sim VS Code Edition extension's code executor API to send code to Isaac Sim and read the log file directly for console output. This allows you to run arbitrary Python code in Isaac Sim and get its results back in your MCP Client.
Prerequisites
- NVIDIA Isaac Sim with the Isaac Sim VS Code Edition extension enabled (
isaacsim.code_editor.vscode) - The extension's code executor must be running and reachable on
127.0.0.1:8226(default)
Installation
pip install isaacsim-mcp
Or for an editable local install:
git clone https://github.com/mochan-b/isaacsim-mcp
cd isaacsim-mcp
pip install -e .
In Isaac Sim, enable the isaacsim.code_editor.vscode extension.
Add to your MCP client.
For example, assuming your virtual environment is located at .venv, in Codex:
codex mcp add isaacsim-mcp -- .venv/bin/isaac-mcp-server
and Claude
claude mcp add isaacsim-mcp -- .venv/bin/isaac-m
Tools exposed to MCP Client
| Tool | Description |
|---|---|
check_isaac_connection |
Test whether Isaac Sim's executor is reachable |
execute_isaac_code |
Run Python code inside Isaac Sim and return its output |
get_isaac_console_errors_warnings |
Read warnings and errors from the Isaac Sim log |
Timeouts
execute_isaac_code has a timeout parameter (default 10 s). For long-running operations such as loading a USD stage or running a simulation loop, pass a larger value:
execute_isaac_code(code="...", timeout=60)
The MCP server is launched by the MCP client.
Standalone CLI
Both helper modules can be used directly without Claude:
# Send code to Isaac Sim
python -m isaac_send --code "import omni; print(omni.__version__)"
python -m isaac_send --file my_script.py
python -m isaac_send --timeout 30 --file long_running.py
# Read Isaac Sim log
python -m isaac_console # last 50 warnings/errors
python -m isaac_console -n 100 -e # last 100 errors only
python -m isaac_console --since 2026-03-01T12:00:00Z
Usage
License
MIT
Metadata
Release files for isaacsim-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| isaacsim_mcp-0.1.0.tar.gz | 70.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| isaacsim_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 78.9 kB
Release files / isaacsim_mcp-0.1.0.tar.gz
| Download URL | isaacsim_mcp-0.1.0.tar.gz |
|---|---|
| Size | 70.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1a78e2facd465ec4b7ae0f206ef50d84bf8af160ad7a15ea0f560bf0d80d51a3
|
|
BLAKE2b-256 checksum How to use checksums |
7b6d77d3b3fcd383f26c1fe94704ccb2b08dfba6bf792ada0cc08c3a5cc6e45f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Hatch/1.16.5 cpython/3.12.3 HTTPX/0.28.1
|
Release files / isaacsim_mcp-0.1.0-py3-none-any.whl
| Download URL | isaacsim_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 8.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
49559408d7da1671b9234dcfd9ac1771a83584fc0d6ebc8e6152871877f98ea1
|
|
BLAKE2b-256 checksum How to use checksums |
5ef38f38f37fca073461705a38c41152c40045e05ed93ff09a9bebd4d317eff3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Hatch/1.16.5 cpython/3.12.3 HTTPX/0.28.1
|
Security for isaacsim-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.