MCP configuration instruction for MeshInspector users

Release v2.5.8 (May 2026) ships McpGateway — a small bridge that lets MCP-compatible AI assistants
such as Claude Desktop, Claude Code, Cursor, and others control MeshInspector: open files, inspect the scene,
press buttons, and run tools.

To enable it, add a MeshInspector entry to your MCP client's config file, for example Claude Desktop's
claude_desktop_config.json.

Windows

{
  "mcpServers": {
    "meshinspector": {
      "command": "C:\\Program Files\\MeshInspector\\MeshInspector\\McpGateway.exe",
      "args": ["--launch-cmd", "MeshInspector"]
    }
  }
}

macOS

{
  "mcpServers": {
    "meshinspector": {
      "command": "/Applications/MeshInspector.app/Contents/MacOS/McpGateway",
      "args": ["--launch-cmd", "MeshInspector"]
    }
  }
}

--launch-cmd MeshInspector tells the gateway which executable to start if MeshInspector is not already
running. The gateway resolves it relative to its own directory and auto-appends .exe on Windows,
so the bare name is enough.

Save the config, restart your MCP client, and the meshinspector server should appear in its connectors
list. Try asking the assistant something like:
"In MeshInspector, list the objects in the current scene".
If MeshInspector is not running yet, the assistant will launch it first.

Linux — we have not validated this on Linux yet, but the pattern is the same:
point command at the bundled McpGateway binary inside your install, for example inside
the AppImage's extracted layout, and keep the --launch-cmd MeshInspector argument.

Advanced options

Custom MCP port

The gateway talks to MeshInspector on 127.0.0.1:7887 by default. If that port is taken, or you want
to run two MeshInspector instances side by side with separate AI sessions, add --mcp-port:

"args": ["--launch-cmd", "MeshInspector", "--mcp-port", "8888"]

The port is forwarded to the spawned MeshInspector and used for the gateway's own probe — one flag moves the
whole loop.

Extra arguments for MeshInspector

To pass additional command-line arguments to MeshInspector when the gateway launches it, use
--launch-arg. This option is repeatable, with one value per flag:

"args": ["--launch-cmd", "MeshInspector", "--launch-arg", "-noSplash", "--launch-arg", "C:\\path\\to\\scene.mru"]

Each --launch-arg adds one token to MeshInspector's command line, in order.