GIMP Studio MCP
A GIMP 3.x MCP server that gives an AI agent full, structured control of GIMP — with real error capture, safety checkpoints, and print/DTF-aware tooling, in both live and headless modes.
Overview
GIMP Studio MCP lets an MCP-compatible AI agent drive GIMP 3.x with 117 structured, parameter-validated tools instead of hand-written GIMP Python. Every tool returns a structured result so output is never lost, even on error, and a GIMP-3 compatibility layer absorbs the known 3.x quirks. The server attaches to a running GIMP or spawns a headless one automatically — the same tools work identically in both modes. It was built for a working print shop's DTF (direct-to-film) pipeline, so DPI awareness and DTF output are first-class.
Features
- 117 tools across 13 groups for full image control
- Structured returns - every tool reports ok/result/stdout/warnings/error, so output is never lost
- Live or headless - one bridge auto-attaches to a running GIMP or spawns a headless GIMP automatically
- Vision-first -
get_bitmapreturns a viewable preview the agent can actually see, for self-verification - Print / DTF tooling - white underbase, edge choke/spread, garment-aware background knockout, halftone separation, gang-sheet and DTF PNG export
- Safety by default - checkpoint/restore, undo/redo, and undo groups around destructive ops
- GIMP-3 compatibility layer - centralizes 3.x gotchas so they don't need relearning per session
Requirements
- GIMP 3.x (verified on 3.0.4 and 3.2.4; GIMP 2.x is not supported)
- Python 3.10+ (for the MCP server)
- An MCP-compatible AI client (Claude Desktop, Claude Code, etc.)
- The GIMP-side bridge, installed with
gimp-mcp install-plugin
Installation
Step 1: Install the Server
pipx install twelvetake-gimp-studio-mcp Prefer to install straight from source? pipx install git+https://github.com/TwelveTake-Studios/gimp-studio-mcp, or clone the repo and run pip install -e .
Step 2: Install the GIMP-side Bridge
Install the bridge into GIMP's plug-ins directory, then verify the setup:
gimp-mcp install-plugin
gimp-mcp doctor Restart GIMP (or it loads on next launch). The bridge auto-starts as a persistent extension. gimp-mcp doctor checks the install, locates the GIMP executable, and round-trips the bridge; add --headless to also spawn and verify a headless GIMP.
Step 3: Register With Your AI Client
Add the server to your MCP client's configuration:
Claude Desktop
Windows: %APPDATA%\Claude\claude_desktop_config.json
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"gimp": {
"command": "gimp-mcp",
"args": ["serve"]
}
}
} Other MCP Clients
For Claude Code, Cursor, Windsurf, or any other MCP-compatible client, add the same server definition to your client's MCP config:
{
"mcpServers": {
"gimp": {
"command": "gimp-mcp",
"args": ["serve"]
}
}
} The server attaches to a running GIMP if one is available, and otherwise spawns a headless GIMP automatically. Set GIMP_MCP_HEADLESS=1 to always run headless.
Available Tools (117)
| Group | Count | What it covers |
|---|---|---|
| Session | 5 | Status, image list, active-image switch, raw exec, namespace reset |
| Document | 4 | New/open image, flatten, export |
| Layers | 18 | Create/duplicate/delete/reorder/move, opacity, blend mode, groups, merge, seam-check |
| Masks & Alpha | 8 | Add/apply/remove masks, alpha add/lock, alpha and selection, luminance to alpha |
| Selections | 14 | Rect/ellipse/by-color/fuzzy/from-path/from-alpha, grow/shrink/feather/border, invert |
| Paint | 10 | Pencil/paintbrush, bucket fill, gradient, stroke, fg/bg + brush + opacity |
| Text | 5 | Create/edit text layers, props, outline, font check/substitute |
| Color & Tone | 10 | Brightness/contrast, levels, curves, hue/sat, color balance, posterize, threshold, normalize |
| Filters & Effects | 4 | Gaussian blur, unsharp mask, drop shadow, generic GEGL apply_filter |
| Print / DTF | 13 | White underbase, edge choke/spread, trim-to-content, garment-aware knockout, halftone, gang sheet, DTF PNG |
| Color Management | 7 | Assign/convert ICC profiles, soft-proof, grayscale/RGB, profile inspect |
| Analysis | 12 | get_bitmap preview, histogram, color-at, region read, metadata, op/procedure listing |
| Safety | 7 | Checkpoint/restore, undo/redo, undo groups, list checkpoints |
Tools are self-describing through your MCP client; describe_op and the list_* tools enumerate ops and resources at runtime.
Usage Examples
General Editing
Open logo.png and tell me its size and layers Add a 12px white outline to the text layer Auto-crop the image to its content, then export a transparent PNG Show me the current canvas DTF (Direct-to-Film)
Knock out the black shirt color behind this artwork Add a white underbase choked 2px so it doesn't peek Clean this up for DTF and export a 300-DPI transparent PNG Gang up 12 copies of this design onto a 22-inch sheet at 300 DPI knockout_background is garment-aware: pass a shirt preset (black, navy, heather gray, red, and more) and it picks the right removal technique for that garment. Run list_shirt_presets to see the catalog.
Security Model
This server runs on the same trust boundary as the local user. It is intended for a single-user workstation and is not a sandbox. Installing it grants any attached AI agent the ability to drive GIMP on your machine.
- Loopback only + token. The bridge listens on 127.0.0.1 with an ephemeral port and a per-session token. It is not exposed to the network.
- Raw exec is arbitrary host code by design. The
gimp_exectool runs Python in GIMP's process. Only attach trusted agents and trusted content. - Disable switch. Set
GIMP_MCP_NO_EXEC=1to skip registeringgimp_execentirely; the other 116 structured tools still work.
See SECURITY.md for the full threat model.
FAQ
Do I need GIMP open to use this?
Not necessarily. The server attaches to a running GIMP if one is available, and otherwise spawns a headless GIMP automatically. The same tools work in both modes.
Which GIMP versions are supported?
GIMP 3.x. It has been verified on GIMP 3.0.4 and 3.2.4, headless and live. GIMP 2.x is not supported.
Is it sandboxed?
No. It runs on the same trust boundary as the local user, and gimp_exec can run arbitrary Python in GIMP's process. See the Security Model above.
Edited the server but tools look unchanged?
The MCP server does not hot-reload. Restart your MCP client session.
Is this affiliated with the GIMP project?
No. This is an independent, unofficial tool that controls GIMP. GIMP is a trademark of its respective owners.
Need a custom MCP server?
We build MCP servers like this one — wiring AI assistants into DAWs, creative software, and internal tools. That is a service we offer. Tell us your workflow and we will scope it.
Get a custom MCP built