Connect GIMP through a live desktop plugin or a separate headless Script-Fu MCP server. For Claude Code, 3 routes are explicitly documented by the integration maintainer.
A persistent headless GIMP Script-Fu process exposes image operations through MCP.
Platforms: Windows, macOS, Linux
The maintainer documents Claude Code setup for this connection.
Node.js 20+ and GIMP 3.x configured with the documented Script-Fu server.
This route runs GIMP headlessly; it does not manipulate the image currently open in the desktop window.
A GIMP 3 plugin connects the running application to an MCP server.
Platforms: Windows, macOS, Linux
The maintainer documents Claude Code setup for this connection.
GIMP 3.2+ with the companion plugin and its documented Python server environment.
This desktop plugin differs from the headless Script-Fu route and needs a compatible running GIMP instance.
A GIMP 3 plugin and MCP server for editing images in a running session.
Platforms: macOS
The integration documentation explicitly names this client.
GIMP 3.2, the GIMP plugin, and the MCP server.
Start the GIMP plugin server for each session; the project evolved from the maorcc bridge.
| Integration | Claude Code compatibility | Requirements |
|---|---|---|
| GIMP MCP · Script-Fu | Documented setup Setup guide | Node.js 20+ and GIMP 3.x configured with the documented Script-Fu server. |
| GIMP MCP · desktop plugin | Documented setup Setup guide | GIMP 3.2+ with the companion plugin and its documented Python server environment. |
| GIMP 3 MCP · tifyr | Documented setup Setup guide | GIMP 3.2, the GIMP plugin, and the MCP server. |
The sources establish the capabilities listed above, not complete application coverage. Check each bridge’s limitations and your application version before starting.
Choose a route that explicitly documents Claude Code and matches your environment. Start with the maintainer’s setup guide and a disposable project copy. Shared MCP support alone is listed as an inference.
All GIMP integrations