GIMP 3 adapter for the DCC Model Context Protocol
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"dcc-mcp-gimp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# dcc-mcp-gimp <p align="center"> <picture> <source media="(prefers-color-scheme: dark)" srcset="docs/assets/dcc-mcp-gimp-dark.svg"> <source media="(prefers-color-scheme: light)" srcset="docs/assets/dcc-mcp-gimp.svg"> <img src="docs/assets/dcc-mcp-gimp.svg" alt="DCC-MCP · GIMP" width="600"> </picture> </p> Production-oriented GIMP 3 adapter for the DCC Model Context Protocol ecosystem.  _Illustrative workflow generated with OpenAI ImageGen from the retained source in `docs/images/sources`; it is not a GIMP screenshot or host-validation artifact._ The adapter keeps GIMP API ownership inside a persistent GIMP 3 Python plug-in. An authenticated loopback JSON-lines bridge accepts a fixed catalog of typed commands, bounds connections, requests, responses, queue depth, image size, layer traversal, paths, file size, and execution time, then marshals every host operation onto GIMP's GLib main thread. It exposes no arbitrary Python, Script-Fu, action, or PDB-procedure execution. <!-- dcc-mcp-coverage-pointer:start --> <!-- Generated from dcc-mcp-catalog.yml by scripts/generate_adapter_pointer.py in dcc-mcp/dcc-mcp-core. Do not edit by hand. --> ## Part of the DCC-MCP host matrix **dcc-mcp-gimp** — GIMP 3 adapter with typed image, layer, save, and production export workflows. It is one of **47 host adapters** in the DCC-MCP catalog. Every adapter speaks the same MCP protocol and builds on the same core runtime contract; each one exposes the tools its own host needs on top of that. - [All host adapters and install metadata](https://dcc-mcp.github.io/ecosystem) - [Host matrix on the core README](https://github.com/dcc-mcp/dcc-mcp-core#readme) - [Showcase](https://dcc-mcp.github.io/showcase) This block is generated from the catalog entry in [`dcc-mcp-catalog.yml`](https://github.com/dcc-mcp/dcc-mcp-core/blob/main/dcc-mcp-catalog.yml). Re-run the generator after changing the catalog. …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.