spektrafilm-mcp
Related Servers
Alternatives to spektrafilm-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceEnables applying deterministic film grain and analog adjustments to photos locally via natural language, with no uploads.MIT- AlicenseBqualityBmaintenanceEnables AI agents to drive a full photo-editing engine through validated, non-destructive operations — exposure and colour grading, effects, geometry, text/watermarks, style matching from a reference image, natural-language looks, and batch processing over folders. Originals stay untouched, edits live in an open JSON project format, and everything runs locally without network access unless opted in.27Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to inspect images, compare and apply 41 dithering algorithms with 256 curated or custom palettes, and produce stills, animations, video, and print separations locally while saving reusable recipes. It exposes these image-processing workflows through typed MCP tools, resources, and prompts, keeping source files and artifacts in a user-controlled workspace.MIT
- FlicenseNot gradedqualityDmaintenanceMCP server enabling AI agents to perform autonomous photographic color science and screenshot annotation with deterministic computer vision, film emulation, and real-time live preview.1-
- AlicenseAqualityAmaintenanceEnables AI agents to perform deterministic, non-generative image transformations—straightening, cropping, masking, layering, color adjustments, and encoding—as reproducible recipes while preserving immutable originals.13MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to scan and search local photo libraries, maintain persistent selections across turns, preview grouping and export plans, and create albums or copy/compress photos while keeping originals in place.MIT
TDQS
Scored across 9 tools
Each tool maps to a distinct stage of the film-lab pipeline (load, recipe, framing, preview variants, detail inspection, export, state, undo), so misselection is unlikely. Minor overlap exists between develop and frame (both mutate state and return a preview with 'only the fields you pass change' semantics), and between loupe and export (both render full-resolution), but the crop-only vs save distinction is stated.
The set mixes verb_noun names (open_image, list_stocks, get_state) with bare verbs (develop, frame, compare, export, undo) and a lone noun (loupe). The darkroom vocabulary keeps it readable, but there is no predictable pattern an agent can extrapolate from.
Nine tools cover the workflow with no filler: one per operation, each earning its place. Well within the ideal 3-15 range for a scoped image-processing server.
The surface covers the full lifecycle: load, inspect stocks, adjust recipe and framing, compare variants, inspect detail, export, and undo. Gaps are minor: no redo/redo-history, no way to save or reload a named recipe preset, and no documented way to reset framing outside a frame() call.