Omniverse MCP Server

What the code does

We read the source, 4 d ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

            bbox_path = os.path.join(h.output_dir, "captures", f"viewport_{capture_id:04d}_bboxes.txt")

    return subprocess.run(  # noqa: S603 - argument lists the gate builds itself; nothing goes through a shell

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add omniverse-mcp -- uvx omniverse-mcp

{
  "mcpServers": {
    "omniverse-mcp": {
      "command": "uvx",
      "args": [
        "omniverse-mcp"
      ]
    }
  }
}

[mcp_servers.omniverse-mcp]
command = "uvx"
args = ["omniverse-mcp"]

{
  "mcpServers": {
    "omniverse-mcp": {
      "command": "uvx",
      "args": [
        "omniverse-mcp"
      ]
    }
  }
}

{
  "servers": {
    "omniverse-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "omniverse-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: PYTHONPATH (Set it empty, so a Python path that Isaac Sim's environment sets stays out of the server's Python), OMNIVERSE_MCP_HOST (The host of the Kit app running the ovmcp.bridge extension), OMNIVERSE_MCP_PORT (The bridge's port in the Kit app), OMNIVERSE_MCP_OUTPUT_DIR (The folder for images and long answers (default: ./mcp_output)), OMNIVERSE_MCP_TOKEN (The bridge's token, for Kit on another machine; on the same machine the server reads it from Kit).