Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CAPTURE_ONE_MCP_TIMEOUT_MSNoFallback Apple Event timeout in milliseconds2000
CAPTURE_ONE_MCP_ALLOW_WRITENoEnables the editing tools. Read-only until set.false
CAPTURE_ONE_MCP_MAX_VARIANTSNoCap on variants returned in one call500
CAPTURE_ONE_MCP_TESTBED_DOCUMENTNoDocument id of a session you are willing to have modified for testing
CAPTURE_ONE_MCP_ALLOW_DESTRUCTIVENoAdditionally enables irreversible verbs. Requires the above.false

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
co_statusA

Health and context for Capture One: whether it is running, whether Apple Events are actually getting through, the reported app version, the open document, and which write tiers are enabled. Call this first when anything else times out.

co_list_documentsA

List the Capture One sessions and catalogs that are currently open, and which one is frontmost.

co_get_documentA

Detailed settings for the current document: kind (session or catalog), paths, session folders, naming/token formats, counters, current collection and recipe, and processing queue depth.

co_list_collectionsA

List the collections in the current document: albums, projects, groups, smart albums, catalog folders and session favorites.

co_set_current_collectionA

Focus a collection in the Capture One browser by name or id. Changes only what is displayed; no image data is touched.

co_list_variantsA

List variants (the editable instances of images) with filtering and pagination. This is the main way to find images. Filter by rating, color tag, pick flag, filename or extension; request extra field groups only when needed, since those cost a round trip per variant.

co_get_variantA

Everything scriptable about one variant: source image and EXIF, all adjustment values, crop, lens correction, IPTC metadata, keywords, layers, and previously written output files.

co_list_recipesA

List the output recipes in the current document, with format and enabled state.

co_get_recipeA

Full settings for one output recipe: file format and quality, scaling, output sharpening, destination and naming, metadata inclusion, crop handling and watermark.

co_list_stylesA

Names of the styles and presets available in Capture One. The scripting interface exposes names only, not their contents.

co_list_keywordsB

Keywords defined in the current document.

co_select_variantsA

Change which variants are selected in Capture One. Selection is view state — no image data, metadata or library structure is modified. Useful to stage a set for the user to look at, or to set up a subsequent selection-scoped call.

co_list_adjustmentsA

List every writable adjustment property with its type, valid range and any quirks. Ranges were recovered by probing the live app — the scripting dictionary declares none. Call this before co_adjust_variants to get exact parameter names and limits.

co_list_layersA

List the layers on variants, with kind, enabled state, opacity and luma-range settings. Layers have no id and are addressed by index; index 0 is always the background layer.

co_list_recipe_propertiesA

List every writable recipe property with its type and allowed values, for use with co_configure_recipe.

co_process_queue_statusA

Current depth of the processing queue, and the jobs still pending.

co_variant_output_filesC

Files previously written for variants, from Capture One's output history, including whether each file still exists on disk.

co_compare_variantsA

Compare readable settings of source and candidate variants from the same image in the expected document. Reports differences and unavailable fields, plus IDs for keeping the candidate or returning to the source. Mask contents, curves and luma ranges are outside comparison coverage.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 18 tools

Disambiguation5/5

Each tool targets a distinct aspect of Capture One—documents, collections, variants, recipes, styles, keywords, adjustments, layers, selection, processing, and output files. Even the list/get pairs are clearly separated by verb, and no two tools overlap in purpose. The only slight overlap is between co_list_documents and co_status, but they serve different functions (listing all open documents vs. health/status).

Naming Consistency4/5

All tools share the 'co_' prefix, and most follow a verb_noun pattern (list_*, get_*, set_*, select_*, compare_*). However, three tools—co_status, co_variant_output_files, and co_process_queue_status—are noun phrases without a verb, breaking the consistency slightly. The pattern is still readable and predictable overall.

Tool Count4/5

With 18 tools, the count is on the higher end of the reasonable range (16-25) but not excessive for a complex application like Capture One. It covers a broad range of features without being bloated, and each tool serves a clear purpose within the domain.

Completeness2/5

The tool set has significant gaps: it references co_configure_recipe and co_adjust_variants but these tools are not present, leaving no way to actually modify recipes or adjustments. Additionally, there are no tools for creating or modifying collections, layers, or applying edits. This incomplete surface will cause agent failures when trying to perform full workflows.

Maintenance

ActivityMaintained
ResponsivenessNo issues