gimp-mcp
AGENTS.md3 starsChanged 4 months agoMITView on GitHub
FastMCP 3.2+ server for professional image editing using GIMP.
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
No bare except: pass — log exceptions
- Very specific: line 27
Use from gimp_mcp.logging_config import get_logger for logging
≈ “Common” is an estimate: at least 1 in 5 of the 36,368 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
gimp-mcp — Agent Context
FastMCP 3.2+ server for professional image editing using GIMP.
Quick Start
uv run python -m gimp_mcp.main # stdio mode (Claude Desktop)
uv run python -m gimp_mcp.main # SSE mode (MCP_PORT=10773)
uv run ruff check src/ # LintPorts
- Frontend: 10772
- Backend: 10773
- GIMP Bridge: 10824
- Logging: 11062
Architecture
- 17 portmanteau tools (gimp_file, gimp_transform, gimp_color, gimp_filter, gimp_layer, gimp_analysis, gimp_batch, gimp_system, gimp_workspace, gimp_channel, gimp_animation, gimp_paths, gimp_parasites, gimp_color_management, gimp_gegl, gimp_gmic, gimp_pdb)
- Dual transport: stdio (default) and SSE/HTTP
- Live bridge (port 10824) + headless CLI modes
- FastMCP 3.2+ sampling, prompts, resources, skills, Prefab UI
Code Rules
- Ruff Python linting (line length 120)
- No bare
except: pass— log exceptions - Use
from gimp_mcp.logging_config import get_loggerfor logging - Tauri native wrapper at
native/
Key Files
| File | Purpose |
main.py | Portmanteau tool registration |
http_app.py | FastAPI web backend |
bridge_wrapper.py | Live GIMP TCP bridge |
cli_wrapper.py | Headless GIMP CLI |
gimp_detector.py | Cross-platform GIMP detection |
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 28,693 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/architect.mdcCursor rule
- llms-full.txtllms.txt
- llms.txtllms.txt
- full-stack-developerSkill
- mcp-server-architectSkill
- gimp-expertSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

