compositor-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inspect_projectA | Reads a Compositor .comp project and returns the canvas info plus every layer in stacking order (bottom to top), with folder depth, visibility, opacity, blend mode and transform. |
| list_layersA | Compact list of layers (id, name, kind, visibility) from top to bottom as shown in Compositor's Layers panel. |
| render_previewA | Flattens the project and returns a PNG preview image so the model can see the composition. Optionally saves it to a file. Clipping masks, adjustment layers and layer effects are not rendered; the response lists what was skipped. |
| export_flattenedA | Renders the whole project at full resolution to a PNG or JPEG file. |
| export_layerA | Copies a pixel layer's source PNG (untransformed, original resolution) or its mask to a file. |
| create_projectA | Creates a new empty .comp project. Optionally adds a solid background layer. Overwrites the manifest of an existing package at that path. |
| add_image_layerA | Imports an image file (PNG, JPEG, HEIC, TIFF, WebP…) as a new pixel layer. The pixels are stored as-is; the placement only sets the layer's transform. |
| add_folderB | Creates an empty layer folder (group). |
| set_layerA | Changes name, visibility, opacity, blend mode, mask enablement or transform (origin, size, rotation, flips) of a layer. Only the given fields change. |
| move_layerA | Reorders a layer (with its subtree if it is a folder): to the top or bottom of a folder or the root, or directly above/below another layer. |
| remove_layerA | Deletes a layer (and, for a folder, everything inside it) together with its image and mask files. |
| replace_layer_imageA | Swaps the source pixels of a pixel layer with another image file, keeping its transform, mask and properties. Use it to round-trip a layer through an external editor or a generated image. |
| set_layer_maskA | Attaches a raster mask from a grayscale image (white reveals, black hides) to a layer, or removes the existing mask. The mask is stretched over the layer's own rectangle. |
| resize_canvasA | Changes the document size without resampling layers. Layers keep their pixels and are offset according to the anchor. |
| open_in_compositorA | Opens (or reloads) the project in the Compositor app on this Mac so the user can see the result. Compositor reads the package from disk on open. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| format |
TDQS
Scored across 15 tools
Each tool targets a distinct action and resource: layer image replacement, mask attachment, canvas resizing, project inspection, layer listing, preview rendering, export operations, project creation, layer/folder addition, property updates, reordering, and deletion. There is no ambiguity between tools; even set_layer and set_layer_mask are clearly separated, with set_layer handling generic properties and set_layer_mask specifically managing raster masks.
All 15 tools follow a consistent verb_noun pattern in snake_case (e.g., replace_layer_image, set_layer_mask, resize_canvas, create_project). The verb is always first, and nouns are descriptive. Even open_in_compositor follows the pattern with a prepositional modifier. No mixed conventions or vague verbs.
With 15 tools, the set is well-scoped for a compositing application. It covers project creation, layer management (add, remove, reorder, modify), rendering, export, and inspection. Each tool serves a clear purpose, and the count is within the ideal range for a domain-specific MCP server.
The tool surface covers the core lifecycle: project creation, layer addition/removal/modification, reordering, masking, image replacement, rendering, and export. Minor gaps exist, such as no explicit save operation (though create_project overwrites manifests) and lack of support for layer effects or duplicate/merge operations. However, agents can complete most workflows without dead ends.