에이전트 강화
게시자의 자체 명령입니다. PlugMCP 엔드포인트가 아닙니다.
Host a copy with our keys and logs.
uvx oid-mcp==0.3.6Claude Code에는 로컬 명령용 설치 링크가 없습니다. 아래 명령을 복사해 터미널에서 실행합니다.
claude mcp add openimagedebugger-openimagedebugger -- uvx oid-mcp==0.3.6터미널에서 실행합니다.
{ "mcpServers": { "openimagedebugger-openimagedebugger": { "command": "uvx", "args": [ "oid-mcp==0.3.6" ] } }}claude_desktop_config.json
원격 URL인가요, 내 컴퓨터에서 실행하는 명령인가요? 두 설치 방식의 차이
PlugMCP에서 실행
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
실행Open Image Debugger is a tool for visualizing in-memory buffers during debug
sessions, compatible with both GDB and LLDB. It works out of the box with
instances of the OpenCV Mat class and Eigen matrices, but can also be
customized to work with any arbitrary data structure.
Prefer VS Code or a fork (Cursor, VSCodium, Windsurf, …)? Skip the manual build — install the extension from the VS Code Marketplace or Open VSX. See Installation below.
New — using CLion or Android Studio? The Open Image Debugger plugin is now on the JetBrains Marketplace: plot buffers straight from the native C/C++ debugger, inside the IDE. See Installation below.
New — declarative custom types. You can now describe your own buffer types in a
.oid/types.jsonfile instead of writing Python; the same file works in gdb, lldb, and the VS Code and JetBrains extensions. See doc/declarative-types.md.
[0, 1], where 0
represents black and 1 represents white.apt installapt install command below. Alternatively, configure with -DNFD_PORTAL=ON to use the xdg-desktop-portal (D-Bus) dialog backend instead of GTK.All other third-party libraries are bundled as git submodules and built from source, so they don't need to be installed:
stb_image, stb_image_write, stb_truetype)Note: this list might get out-of-date by accident. For a more accurate list of requirements, please check what is used in https://github.com/OpenImageDebugger/OpenImageDebugger/blob/main/.github/workflows/build.yml and in the CI container images defined in https://github.com/OpenImageDebugger/dockerfiles.
The quickest way to get started is the Open Image Debugger extension, available for VS Code and compatible forks (Cursor, VSCodium, Windsurf, and others):
The Open Image Debugger plugin brings the same viewer to JetBrains IDEs with a native C/C++ debugger — CLion, and Android Studio with the NDK:
If you'd rather build and integrate the desktop version manually, follow the steps below.
On Ubuntu, you can install most of the dependencies with the following command:
sudo apt install build-essential cmake libgl1-mesa-dev libgtk-3-dev libpython3-dev \
python3-dev libwayland-dev libxcursor-dev libxi-dev libxinerama-dev \
libxkbcommon-dev libxrandr-dev pkg-config
Clone the source code to any folder you prefer and initialize the submodules:
git clone https://github.com/OpenImageDebugger/OpenImageDebugger.git --recurse-submodules
Now run the following commands to build it:
cmake -S . -B build -DCMAKE_INSTALL_PREFIX=/path/to/installation/folder
cmake --build build --config Release --target install -j 4
GDB integration: Edit the file ~/.gdbinit (create it if it doesn't exist)
and append the following line:
source /path/to/OpenImageDebugger/oid.py
LLDB integration: Edit the file ~/.lldbinit (create it if it doesn't
exist) and append the following line:
command script import /path/to/OpenImageDebugger/oid.py
At the moment, the MacOS build is only known to work with python3 and lldb
installed from Homebrew (the system-provided LLDB from the
Xcode Command Line Tools is not supported). Install them with:
brew install python3 llvm
Make sure python3 resolves to the Homebrew one — run which python3 and
confirm it points under the Homebrew prefix (/opt/homebrew on Apple Silicon,
/usr/local on Intel; brew --prefix prints it), rather than a pyenv, conda or
system Python. The standard Homebrew install puts that prefix's bin on your
PATH.
Then debug your program using the Homebrew LLDB, for example:
BREW_PREFIX=$(brew --prefix)
"$BREW_PREFIX"/opt/llvm/bin/lldb /path/to/your/executable
After compiling the plugin, you can test it by running the following command (use the same Python 3 interpreter CMake found when building):
python3 /path/to/OpenImageDebugger/oid.py --test
On MacOS, invoke the test with the full path to the Homebrew python3, for
example:
BREW_PREFIX=$(brew --prefix)
"$BREW_PREFIX"/bin/python3 /path/to/OpenImageDebugger/oid.py --test
If the installation was succesful, you should see the Open Image Debugger window
with the buffers sample_buffer_1 and sample_buffer_2.
When the debugger hits a breakpoint, the Open Image Debugger window will be
opened. You only need to type the name of the buffer to be watched in the
"add symbols" input, and press <enter>.
You can also open an image or NumPy array in the viewer without a debugger
session at all, either from the File → Open menu (shortcut Ctrl+O) or
from the command line.
From the command line, pass one or more files with the repeatable -o /
--open flag:
oidwindow --open path/to/image.png --open path/to/array.npy
Supported formats:
Files opened this way are shown alongside any debugger buffers, but they are never reported back to a debugger and are not saved as session state.
Linux build note: the native file dialog requires GTK 3 (
libgtk-3-dev) at build time, or configure with-DNFD_PORTAL=ONto use the xdg-desktop-portal (D-Bus) backend instead. MacOS and Windows need no extra packages.
Open Image Debugger does not register itself as a system handler for these
file types; use the File → Open menu or the --open flag to load them.
The (min) and (max) fields on top of the buffer view can be changed to control autocontrast settings. By default, Open Image Debugger will automatically fill these fields with the mininum and maximum values inside the entire buffer, and the channel values will be normalized from these values to the range [0, 1] inside the renderer.
Sometimes, your buffer may contain trash, uninitialized values that are either too large or too small, making the entire image look flat because of this normalization. If you know the expected range for your image, you can manually change the (min) and (max) values to focus on the range that you are interested.
Sometimes you want to compare two buffers being visualized, and need to zoom in
different places of these buffers. If they are large enough, this can become a
very hard task, especially if you are comparing pixel values. This task is made
easier by the lock buffers tool (which is toggled by the button with a chain
icon).
When it is activated, all buffers are moved/zoomed simultaneously by the same
amount. This means you only need to align the buffers being compared once;
after activating the lock buffers mode, you can zoom in anywhere you wish in
one buffer that all other buffers will be zoomed in the same location.
If you need to quickly move to any pixel location, then the go to
functionality is what you are looking for. Press Ctrl+L and two input fields
corresponding to the target destination in format <x, y> will appear at the
bottom right corner of the buffer screen. Type the desired location, then press
enter to quickly zoom into that location.
Sometimes you may want to export your buffers to be able to process them in an external tool. In order to do that, right click the thumbnail corresponding to the buffer you wish to export on the left pane and select "export buffer".
Open Image Debugger supports two export modes. You can save your buffer as a PNG
(which may result in loss of data if your buffer type is not uint8_t) or as a
binary file that can be opened with any tool.
Buffers exported in the Octave matrix format can be loaded with the function
oid_load.m, which is available in the matlab folder. To use it, add this
folder to Octave/Matlab path variable and call
oid_load('/path/to/buffer.dump').
Open Image Debugger ships an experimental MCP server (oid-mcp) that
lets AI coding agents inspect your buffers in a live gdb/lldb session —
list observable symbols at a breakpoint, view renderings, read exact
values, dump lossless .npy copies, and mirror buffers into the viewer.
Agents can also control and read back a running viewer's view — pan,
zoom, rotate, channel, and auto-contrast — including one opened
standalone with no debugger attached. It is opt-in (launch the debugger
with OID_AGENT=1) and exposes debuggee memory to local processes, so
enable it only in trusted, local development.
See resources/oidmcp/README.md for
deployment and usage instructions.
By default, the plugin works with several data types, including OpenCV's Mat,
CvMat and IplImage and Eigen's Matrix and Map.
Supported library versions: OpenCV 2–5 and Eigen 3.x. The OpenCV
Mat/CvMat channel count is read from the type-flag bit packing in a
version-adaptive way, so both the pre-5 and the OpenCV 5 layouts resolve
correctly; CvMat and IplImage are the legacy C API and therefore apply
only to OpenCV builds that still expose it (4.x and earlier).
To support a different buffer type, describe it in a .oid/types.json file at
your workspace root — no Python required. The common case is five fields:
{
"version": 1,
"types": [
{ "match": "^MyImage$",
"pointer": "{sym}.data",
"width": "{sym}.w",
"height": "{sym}.h",
"dtype": "float32" }
]
}
The same file is read by gdb, lldb, and the VS Code and JetBrains
extensions. You can also
point OID at files outside the workspace with the OID_TYPES_PATH environment
variable. The full format — every field, the expression grammar, dtype names,
discovery and precedence, and a walkthrough migrating an existing Python
inspector — is documented in
doc/declarative-types.md, and the built-in types in
resources/oidscripts/oidtypes/builtin_types.json double as a worked-example
gallery.
The original Python path is still supported for cases the declarative format
cannot express, but it is no longer the preferred approach for new types.
Implement a TypeInspectorInterface subclass from
resources/oidscripts/oidtypes/interface.py; see
doc/python-inspectors.md for the full instructions —
the interface methods, the buffer-metadata dictionary contract, and the debug
decorators.
Open Image Debugger remembers its window size and position, the width of the
symbol list pane, the auto-contrast and link-views toggles, the buffers you
viewed last, and the directory you last exported to. The application writes
this state itself — it is not a preferences file meant to be edited by hand —
and keeps it in OpenImageDebugger/imgui_settings.json under:
Delete that file while the viewer is not running to restore the defaults — a running viewer rewrites it shortly after any change to that state, and again when it exits. This is the fix if the viewer reopens at a window position that is off-screen.
An advanced in-memory image visualization plugin for GDB and LLDB on Linux, with experimental support for MacOS and Windows. Previously known as gdb-imagewatch. Also available as an extension for VSCo
{ "mcpServers": { "openimagedebugger-openimagedebugger": { "command": "uvx", "args": [ "oid-mcp==0.3.6" ] } }}개요
An advanced in-memory image visualization plugin for GDB and LLDB on Linux, with experimental support for MacOS and Windows. Previously known as gdb-imagewatch. Also available as an extension for VSCode and forks
도구
아직 도구 목록이 없습니다. 원격 서버는 첫 상태 확인 후에 도구 목록이 생깁니다.
FAQ
이 페이지에서 Cursor, Claude Desktop, Claude Code 또는 VS Code용 stdio 설정을 복사합니다. PlugMCP 프록시가 아니라 게시자의 설치 방식을 사용합니다.
이 레코드에는 필수 환경 변수가 등록되어 있지 않습니다.
OpenImageDebugger은(는) stdio를 통해 로컬에서 실행됩니다.
마지막 확인: 2026-10-26. An advanced in-memory image visualization plugin for GDB and LLDB on Linux, with experimental support for MacOS and Windows. Previously known as gdb-imagewatch. Also available as an extension for VSCode and forks