Typed in-process and CLI RawTherapee adapter for mcp-photo-edit
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":"mcp-photo-edit-rawtherapee","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.
# mcp-photo-edit-rawtherapee RawTherapee implementation behind the public `mcp-photo-edit-core` models. The same synchronous service can be called directly in-process or through a small JSON CLI boundary. RawTherapee is the first renderer. The executable is resolved in this order: 1. use `rawtherapee-cli` when it is available on `PATH`; 2. otherwise use the absolute executable path in `RAWTHERAPEE_CLI`; 3. otherwise return a structured `BACKEND_UNAVAILABLE` error. Windows PowerShell example when RawTherapee is installed but not on `PATH`: ```powershell $env:RAWTHERAPEE_CLI = "C:\Program Files\RawTherapee\5.12\rawtherapee-cli.exe" mcp-photo-edit-rawtherapee request.json ``` Relative values and paths that do not point to an existing file are rejected. ```python from mcp_photo_edit_rawtherapee import RawEditService response = RawEditService().execute(request) ``` ```shell mcp-photo-edit-rawtherapee request.json ``` Development gates: ```shell uv sync uv run ruff format --check . uv run ruff check . uv run basedpyright uv run pytest uv run python -m build ```
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.