gimp-mcp
Let an AI assistant inspect and edit images in your running GIMP through the Model Context Protocol: layers, text, selections, filters, files, previews. Linux, GIMP 3.2+. MIT licensed.
Quickstart
You need uv and an MCP client (Claude Code, Claude Desktop, VS Code, Cursor…). On Ubuntu 26.04:
sudo apt install -y gimp python3-gi gir1.2-gimp-3.0 # GIMP 3.2+ (other distributions and Flatpak: see below)
uvx gimp-mcp setup # installs the GIMP plug-in, adds the server to your MCP clients
uvx gimp-mcp doctor # after (re)starting GIMP: every check should be [ok]
Then ask your assistant: "Use GIMP to create a 1280×720 image with the title 'Hello' and export it to ~/hello.png".
- Other distributions (Arch, Debian 14, Fedora 44, openSUSE Tumbleweed, Alpine 3.24) and their packages:
compatibility.
GIMP from Flathub works too:
flatpak install flathub org.gimp.GIMP, then the twouvxcommands. - Step-by-step per client: Claude Code, Claude Desktop, VS Code and Cursor, any other MCP client.
- Something wrong?
uvx gimp-mcp doctorsays what and how to fix it (troubleshooting).
Also listed in the official MCP registry
as io.github.mhbxyz/gimp-mcp (from the first PyPI release on).
What it can do
52 tools: inspect images and layer trees, previews, create/open/save XCF/export PNG and JPEG, layers and groups, resize/crop/transform, selections and masks, painting, brightness/contrast, hue/saturation, blur (destructive or editable filters), editable text, undo groups and checkpoints, and allowlisted access to ~420 GIMP procedures. See the tool reference and the coverage matrix.
Demo
uv run demo/thumbnail.py # from a checkout: isolated headless GIMP, outputs in demo/out/
Builds a 1280×720 thumbnail through MCP only (blurred backdrop with editable corrections, masked photo, banner, editable title, a badge undone and redone with checkpoints), saves and reopens the XCF, exports PNG and JPEG, and writes a report of every call and check. Walk-through: docs/guide-thumbnail.md.
Documentation
- Installation reference (manual install, upgrade, uninstall) · MCP clients · troubleshooting · compatibility
- Tool reference · coverage matrix
- Architecture · bridge protocol · security · decisions
- Testing · releasing · GIMP behaviour notes · changelog
1 maintainer
Metadata
1 maintainer
Release files for gimp-mcp 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| gimp_mcp-0.2.0.tar.gz | 75.3 kB | With provenance | Details for gimp_mcp-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gimp_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for gimp_mcp-0.2.0-py3-none-any.whl |
Total release size: 166.3 kB
Release files / gimp_mcp-0.2.0.tar.gz
| Download URL | gimp_mcp-0.2.0.tar.gz |
|---|---|
| Size | 75.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
64be25eed45fb1e12e61e40d62d35f0a86f50c6bc2fc8558e8abaaa04e19089b
|
|
BLAKE2b-256 checksum How to use checksums |
eb70c4a9ffaf5db1af08fd384aad8841dac2d92e45906c99a47ee6fdac7ec0a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 7, 2026.
Transparency logRelease files / gimp_mcp-0.2.0-py3-none-any.whl
| Download URL | gimp_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 91.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
97b9a6f5ee0016eae69b7c0c764ca5400aa64c1d713ecd421fb801ab6202f8e7
|
|
BLAKE2b-256 checksum How to use checksums |
c050cf33a99398f6ae585fb5b14a8253fd041771bbce5980e6a0155a31397c66
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 7, 2026.
Transparency logSecurity for gimp-mcp 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for gimp_mcp-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 7, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
