Skip to main content
Glama
iscca

Capture One AI MCP Server

by iscca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Capture One AI MCP Server

No user-submitted related servers found.

    Related Servers

    • Capture One AI Windows

      ggssghatsys-beep
      A
      license
      C
      quality
      C
      maintenance
      Enables vision-capable AI clients to read and adjust Capture One on Windows through an MCP stdio server (plus a JSON CLI), applying exposure, curves, color, layer and mask edits and returning real Capture One-rendered previews. It runs a local bridge to C1's native parameters with no presets, screenshots or synthetic input.
      6
      MIT

    • io.github.Dongwu259/photo-s

      Dongwu259
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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

    • capture-one-mcp

      byjustinjones
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables automating Capture One Pro on macOS, providing tools for reading and editing images, managing layers/masks, recipes, and processing with risk-tiered write gating.
      18
      2
      MIT

    • LightroomForge

      cyZhu98
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to drive Adobe Lightroom Classic directly — searching and organizing catalogs, reading and writing the full set of develop parameters, building geometric and AI-generated masks (sky, subject, mountains, water, people), applying presets, and rendering previews, histograms, and exports. All capabilities are exposed as 167 MCP tools over a Lua plugin bridge, with write-confirmation sentinels so silently dropped edits surface as explicit errors.
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 6 tools

    Disambiguation3/5

    The six tools have broad functional boundaries, but context, read, and operations overlap: context reads workflow/unresolved operations, read reads native parameters, and operations also returns receipts/tasks/analysis. operations is a catch-all that includes restore writes via adjust and compare/checkpoint links to preview, so agents must read carefully to choose correctly.

    Naming Consistency3/5

    All names are lowercase single words, which is visually consistent, but they mix imperative verbs (read, adjust) with nouns (context, images, operations, preview). There is no predictable verb_noun pattern, though the names remain short and readable.

    Tool Count4/5

    Six tools is a reasonable count for a complex photo-editing integration, and each maps to a recognizable phase: context, read, adjust, images, preview, and operations. However, operations bundles far too many distinct actions, so the set is slightly under-segmented rather than over-counted.

    Completeness4/5

    The surface covers app context, parameter reading, structured adjustments, image selection, previews, receipts, and task/brief workflows, which is broad lifecycle coverage for Capture One editing. Minor gaps remain around explicit final export/save, undo/history, and possibly layer deletion, but core workflows are represented.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources