gimp-agent-mcp
Related Servers
Alternatives to gimp-agent-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to perform structured, semantic artwork editing in GIMP 3 through session-based tools for layers, selections, text, transforms, non-destructive filters, previews, and image export, backed by snapshot undo/redo and XCF-persisted sessions. It also offers a live control center and operation event timeline for observing and managing edits, plus PDB search for expert discovery.28MIT
- AlicenseBqualityBmaintenanceEnables controlling GIMP 3 locally through natural language, providing tools for image editing, layer management, selections, and PDB procedure invocation. Keeps all images and files on the user's machine with a local-first, secure design.401GPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to control GIMP for image editing tasks such as opening, resizing, filtering, exporting, and batch processing images through Python-Fu scripting.36 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to create, paint, edit, inspect, and export images in a running GIMP 3.2 instance via MCP.59 PyPIGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to control GIMP 2.10 through its Script-Fu server, providing access to the entire GIMP procedure database with a vision feedback loop for iterative editing.6AGPL 3.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to perform GIMP-style image operations such as open, resize, crop, flip, rotate, blur, desaturate, text overlay, export, and batch processing via MCP tools, supporting both mock (Pillow) and live GIMP backends.1MIT
TDQS
Scored across 32 tools
Most tools target a clear resource and action pair, so agents can generally tell images, layers, filters, PDB, fonts, and recipes apart. The main overlaps are gimp_pdb_call vs gimp_run_python, which both allow arbitrary GIMP operations, and gimp_layer_effects vs gimp_layer_effect, which differ only by plural and could be mis-selected.
All names share the gimp_ prefix and use snake_case, which helps predictability. However, conventions are mixed: some tools are verb-first (gimp_list_images, gimp_open, gimp_export) while others are noun-first with an action parameter (gimp_layer, gimp_path, gimp_select), and gimp_layer_effects vs gimp_layer_effect is an easily confused singular/plural pair.
With 32 tools, this exceeds the 25-tool threshold for a heavy tool surface. While GIMP is a broad domain, several tools are generic escape hatches or overlapping (gimp_pdb_call, gimp_run_python, recipe tools), making the set feel larger than necessary.
The surface covers session lifecycle, image create/open/export/close, layer and mask operations, selections, filters, paths, text, measurement, PDB access, and scripting, so core GIMP automation workflows are largely complete. Minor gaps exist for direct image-level operations like resize, rotate, and undo, though gimp_pdb_call and gimp_run_python can work around those.