LazyRoom MCP Server
Related Servers
Alternatives to LazyRoom MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceEnables AI agents and users to edit images through natural language, performing layered, non-destructive operations like masks, clipping masks, blend modes, filters, generative fill, image-to-image, background removal and upscaling, either locally or via the user's own API keys. Agents can preview rendered results, measure image properties, review their own work and export finished images through 62 tools shared with the editor's UI.6246 PyPI9MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to run cross-platform batch photo-processing workflows—including RAW decoding, adjustments, noise reduction, white balance, LOG restoration, EXIF tagging, deduplication, selection, HTML galleries, folder watching, and presets—through a unified versioned JSON contract. It also exposes MCP tools for processing, suggestions, autopilot, indexing, search, selection, HDR, face blurring, and more.MIT
- AlicenseNot gradedqualityBmaintenanceEnables local, offline AI editing and enhancement of photos, including scene-aware adjustments, restoration, colorization, upscaling, object/background removal, quality scoring, batch processing, and a before/after web viewer.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to run a complete photo-lab and print-shop workflow locally through tools for file inspection, batch conversion, colour correction, print-sheet layout, PDF text extraction and editing, and windowless printing. Printing supports dry runs and PDF output so source files are never modified.1AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to process images locally via file paths—converting, resizing, removing backgrounds, smart cropping, upscaling, reading or stripping metadata, and batch processing—without files ever leaving the device.MIT
- AlicenseNot gradedqualityCmaintenanceEnables external AI agents to programmatically inspect, edit, and export image documents through tools for layers, selections, painting, adjustments, masks, history, and compositing.MIT
TDQS
Scored across 27 tools
The set has a clear layered architecture: discovery (get_capabilities/list_operations/describe_operations), project lifecycle (open/get_state/edit/history/render/export/save), style (analyze_style/match_style/presets), batch (start_batch/job_status/cancel_job), and a meta-tool layer (list_tools/describe_tool/run_tool). Most tools target a distinct resource+action, but a few pairs are easy to confuse: inspect_image vs analyze_style (both measure tone/colour/grain), and apply_preset vs match_style vs plan_edit all "add steps that create a look". The generic compare utility inside list_tools also overlaps compare_versions.
The dominant pattern is verb_noun (open_image, edit_project, render_preview, apply_preset, delete_preset, list_presets, match_style), which is easy to generalize from. Deviations are minor: two noun-phrase names (project_history, job_status) and an action/noun split in the batch family (start_batch, cancel_job, job_status). Readable throughout, just not perfectly uniform.
27 tools is heavy for a single server and sits above the comfortable 3-15 band. The count is partly mitigated by the meta-tool consolidation (list_tools/describe_tool/run_tool fold dozens of utilities into three entries), but the project/preset/style/batch surface still exposes a lot of individual endpoints an agent must choose among.
Coverage is broad: open (image or .lazyroom), inspect, edit atomically, history/undo/revert, preview, full-res export, save, presets CRUD, style analysis and matching, batch processing with progress/cancel, and a capabilities manifest. Remaining gaps are modest: no explicit close/discard/delete-project operation, and no direct 'add step by operation id without params lookup' shortcut, but agents can work around both.