GIMP MCP
The MCP server gives agents GIMP image editing with visual previews, layers, filters and file export operations.
- 290 ★ on the repository
- Last commit
- GPL-3.0
Broad access
Why this level
- The agent edits and exports images, and `call_api` runs arbitrary Python-Fu with GIMP process permissions.
Install
- Works in
Manual install
git clone https://github.com/gimp-mcp/gimp-mcp.git
cd gimp-mcp
uv syncFirst Quick Start block. Install and enable the in-GIMP plugin separately after dependencies.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent edits and exports images, and `call_api` runs arbitrary Python-Fu with GIMP process permissions.
This is third-party code. Review the repository files before installing.
What it does
GIMP MCP connects agents to a running GIMP editor. Agents change layers, selections, color and size, then inspect image previews. Region snapshots support detailed checks without intermediate disk saves. A Python MCP server talks to a GIMP plugin. Tools cover editing and batch export, with Python-Fu execution for unsupported operations. Users can retain a layered XCF project and a separate exported image.
Who it is for. Designers delegating sequential raster-image edits while inspecting results in GIMP.
Good fit when
- Background removal needs close-up inspection of remaining pixels.
- Several open images need a common export size.
- Text edits must preserve layered source files.
- The agent needs visual feedback after significant edits.
Not a fit when
- Python execution inside GIMP must be prohibited.
- The machine only has GIMP 2.x.
- You expect guaranteed correct retouching without inspecting output.
Example request
Remove the background from an image copy, show a close-up of edges and wait for review before export.MCP
- Transport
- stdio
- Authentication
- not required
Limitations
GIMP 3.2 or later, Python 3.11 or later and uv are required, so verify installed versions before setup. GIMP must be running with an image and its MCP plugin enabled before the external server can connect. Minor GIMP upgrades can change the user-plugin directory, so verify the active path after updating. The `call_api` tool executes arbitrary Python-Fu inside the editor; use file copies and do not expose it to an untrusted agent.
How to disable. Stop the GIMP MCP plugin and remove the client server. Save needed XCF and export files; disabling does not undo edits.
FAQ
Where do I enable it in GIMP?
Open an image and choose Tools, MCP, Start MCP Server.
How do I check the plugin directory?
Open Preferences, Folders, Plug-ins in GIMP and use the active directory.
Can I preserve layers?
Yes. XCF saving retains layers and project metadata.
How do I undo an edit?
Ask the agent to undo the last edit. The server supports undo and redo in image history; inspect a fresh preview afterward.
Why did it disappear after an update?
The GIMP user directory may have changed version. Install the plugin into the new directory and restart.
Discussion
No questions or reviews yet.
Related
MCP serversAn MCP server for Adobe Photoshop: background removal, retouch, social export and batch jobs by chat
An MCP server that edits images through Photopea: layers, text, effects and export, 46 tools for Claude Code and Cursor.
A local MCP server for editing and analyzing images: the agent crops frames, finds objects and reads text from photos
An MCP server for Windows that drives an installed Photoshop: documents, layers and arbitrary JSX scripts
Recraft's remote MCP server: an agent draws raster and vector images, edits a region, removes the background and upscales
An MCP server linking an agent to a Lightroom Classic catalog: photo search, ratings, develop settings, collections, export.
README in short
Batch tools cover resizing, icons, sprite sheets and web exports. State snapshots can target a region for detailed inspection.