dcc-mcp-photoshop — Core Photoshop adapter for DCC-MCP — Python bridge for a
Photoshop UXP plugin with one-click installer.
It is one of 47 host adapters in the DCC-MCP catalog. Every adapter speaks the same
MCP protocol and builds on the same core runtime contract; each one exposes the tools
its own host needs on top of that.
Adobe Photoshop MCP adapter for AI agents to edit documents, layers, text and images through the shared adobepy UXP bridge and typed tools in the DCC-MCP ecosystem.
This block is generated from the catalog entry in
dcc-mcp-catalog.yml.
Re-run the generator after changing the catalog.
Agent workflow
AI agents should use the shared gateway through dcc-mcp-cli; IDE users may
continue to use the MCP endpoint. Prefer typed skills and tools over raw scripts.
Install or update the CLI
dcc-mcp-cli is the preferred control path for every shell-capable agent. If
it is missing, ask the user before installing the latest official release:
# Linux/macOS
curl -fsSL https://raw.githubusercontent.com/dcc-mcp/dcc-mcp-core/main/scripts/install-cli.sh | sh
# Windows PowerShell
powershell -ExecutionPolicy Bypass -c "irm https://raw.githubusercontent.com/dcc-mcp/dcc-mcp-core/main/scripts/install-cli.ps1 | iex"
Keep an official build current through the release manifest:
dcc-mcp-cli update check
dcc-mcp-cli update apply
update apply downloads and stages the latest CLI for the next launch. It
does not update a running dcc-mcp-server; update that server in its own
environment.
dcc-types reports release-catalog support; list reports live sessions. If a
tool belongs to an inactive progressive skill, call dcc-mcp-cli load-skill <skill-name> --dcc-type photoshop before retrying. For post-task improvement,
attach a stable session id with --meta-json, query dcc-mcp-cli stats --range 24h --session-id <task-id>, then pass the bounded evidence to the
review_skill_improvement prompt from dcc-mcp-skills-creator.
Bring Adobe Photoshop to MCP-native AI agents.
dcc-mcp-photoshop turns Photoshop into a standards-compliant MCP Streamable HTTP backend via the adobepy Rust broker and UXP bridge. Agents can inspect documents, create and edit layers, apply text, filters, smart objects, selections, export images, and automate Photoshop workflows through typed tools instead of brittle ad-hoc scripts.
The Python MCP server communicates with Photoshop through the adobepy Rust broker (port 47391), which proxies between the Python SDK and the UXP bridge running inside Photoshop.
Why Use It
What you get
Why it matters
40+ typed Photoshop tools across 8 bundled skill packages
Agents can call validated tools for document, layer, image, text, selection, filter, smart object, and script operations.
adobepy Rust broker
High-performance local proxy between Python SDK and UXP bridge.
Sidecar isolation
Python MCP server runs outside Photoshop's UI thread; adobepy broker handles all host communication.
Gateway compatible
Works with dcc-mcp-server sidecar for multi-DCC deployments alongside Maya, Houdini, Blender, etc.
Multi-channel distribution
Available as a PyPI package or standalone adapter binary; the host bridge ships with adobepy.
Canonical lifecycle
One cross-platform CLI owns plan, staged install, receipt, repair, rollback, verify, and uninstall.
Quick Start
Prerequisites
Follow the cross-platform Install SOP. It documents the pinned
official adobepy CLI checksum release, env-only token contract, Adobe-signed
Photoshop product attestation, and the currently blocked bounded UXP bootstrap.
1. Choose an installation path
For an Internal deployment with an approved prebuilt UXP bridge, use the
studio's approved deployment tooling to create the Adobe debug-plugin link.
The current dcc-mcp-cli install contract does not accept bridge source or
debug-root arguments, so do not pass undocumented --plugin-source or
--adobe-debug-root options. Skip dcc-mcp-photoshop install --json --yes
for this path; it generates and owns a different bridge lifecycle.
After the approved link is created, restart Photoshop and wait for the bridge
to load before running dcc-mcp-cli list,
dcc-mcp-cli wait-ready --dcc-type photoshop, and
dcc-mcp-photoshop verify --json. A filesystem link alone is not live
readiness.
For non-Internal deployments, install and use the adapter-owned lifecycle:
Point your MCP client to the gateway URL. The gateway auto-discovers which DCC (Photoshop, Maya, etc.) to route each tool call to, so you only need one endpoint:
Document information, listing, and lifecycle management.
Tool
Description
Read-only
get_document_info
Get metadata about the active Photoshop document (name, size, resolution, color mode)
✅
list_documents
List all currently open Photoshop documents with metadata
✅
open_document
Open an existing local image or Photoshop document and make it active
❌
list_layers
List all layers in the active document. Set include_hidden=false to exclude hidden layers
✅
close_document
Close a Photoshop document by ID or the active document
❌
photoshop-image
Document creation, export, canvas/image resize, flatten, and merge operations.
Tool
Description
Read-only
create_document
Create a new document with specified dimensions, resolution and color mode
❌
export_document
Export the active document to PNG, JPG, TIFF, or PSD
❌
save_document
Save the active document in its current format
❌
resize_canvas
Resize canvas without scaling content
❌
resize_image
Scale the image (resamples content)
❌
flatten_image
Flatten all layers into a single background layer
❌
merge_visible_layers
Merge all visible layers
❌
photoshop-layers
Full CRUD for layers plus visual property changes.
Tool
Description
Read-only
create_layer
Create a pixel, group, or adjustment layer
❌
delete_layer
Delete a named layer
❌
duplicate_layer
Duplicate a named layer
❌
rename_layer
Rename a layer
❌
set_layer_opacity
Set opacity (0-100) of a named layer
❌
set_layer_visibility
Show or hide a named layer
❌
set_layer_blend_mode
Set blend mode (normal, multiply, screen, overlay, etc., 27 modes)
❌
fill_layer
Fill a layer with solid color (hex) or transparent
❌
photoshop-text
Text layer creation, editing, and inspection.
Tool
Description
Read-only
create_text_layer
Create a new text layer with content and styling (font, size, color, alignment)
❌
update_text_layer
Update text content or style of an existing text layer
❌
get_text_layer_info
Get text content and style properties of a text layer
✅
photoshop-selection
Selection creation, modification, and saving.
Tool
Description
Read-only
get_selection
Get current selection bounds (top, left, bottom, right)
✅
select_all
Select the entire canvas
❌
deselect
Deselect any active selection
❌
select_rectangle
Create a rectangular selection (top, left, bottom, right in pixels)
❌
select_ellipse
Create an elliptical selection
❌
inverse_selection
Invert the current selection
❌
expand_selection
Expand selection by N pixels
❌
contract_selection
Contract selection by N pixels
❌
feather_selection
Feather selection by N pixels
❌
save_selection
Save selection as a named alpha channel
❌
photoshop-filter
Apply filters to layers.
Tool
Description
Read-only
apply_gaussian_blur
Apply Gaussian Blur (radius in pixels)
❌
apply_high_pass
Apply High Pass filter (radius in pixels)
❌
apply_sharpen
Apply Sharpen filter
❌
apply_smart_blur
Apply Smart Blur (radius + threshold)
❌
apply_filter
Generic filter by method name with arguments
❌
photoshop-smart-object
Smart Object operations for non-destructive editing.
Tool
Description
Read-only
convert_to_smart_object
Convert the active layer to a Smart Object
❌
new_smart_object_via_copy
Create a new Smart Object by duplicating the active layer
❌
edit_smart_object_contents
Open the Smart Object for editing
❌
replace_smart_object_contents
Replace Smart Object contents with an external file
❌
photoshop-script
Execute named Photoshop Actions for advanced automation.
Tool
Description
Read-only
execute_action
Execute a named Photoshop Action from an Action Set
❌
photoshop-adjustment
Channel operations and low-level batchPlay access.
Tool
Description
Read-only
batch_play
Execute raw ActionDescriptor batchPlay commands
❌
get_channels
Get channel information for the active document
✅
add_channel
Add a new alpha channel
❌
remove_channel
Remove a named channel
❌
Runtime Features
Feature
Surface
Capability manifest
dcc_capability_manifest({"loaded_only": false}) returns a compact index of loaded and unloaded Photoshop skills.
adobepy broker
Local Rust proxy (port 47391) with session management and timeout control.
Persistent logging
Logs written to ~/.dcc-mcp/logs/ (configurable via DCC_MCP_PHOTOSHOP_LOG_DIR).
Lazy skill loading
load_skill meta-tool expands the tool surface on demand.
Canonical Installer
The dcc-mcp-photoshop CLI is the only lifecycle owner. The legacy
photoshop-setup skill and PowerShell script remain discoverable compatibility
routes, but they delegate operators to the same contract.
load_skill("photoshop-setup")
Tools
Tool
Description
check_environment
Check system prerequisites (Python, pip, Photoshop)
install_package
Install or upgrade dcc-mcp-photoshop via pip
setup_uxp_plugin
Redirect legacy calls to the canonical install lifecycle
start_server
Start server in dev mode for testing
verify_connection
Verify bridge connection to Photoshop
configure_mcp_client
Auto-configure MCP client configs for Claude Desktop, Cursor, VS Code
See install.md for the standard verbs, flags, JSON schema, exit
codes, three-platform host paths, repair behavior, receipt-only uninstall, and
verify-to-usable acceptance gate.
Installation
Use the canonical Install SOP for host integration. Installing a
wheel alone does not load the UXP bridge or prove Photoshop readiness.
The canonical lifecycle uses the approved adobepy CLI through env-only
authentication, stages the generated bridge, commits a redacted receipt, and
then requires a real Photoshop RPC. See install.md; direct bridge
generation is not a second supported installer surface.
The gateway URL (:9765) is a unified facade that aggregates tools from all registered DCCs. On tools/call, the gateway auto-discovers the correct DCC instance via the capability index — no need to specify the DCC type in the URL.
Shared FileRegistry directory for gateway discovery
~/.dcc-mcp/registry
DCC_MCP_PHOTOSHOP_SKILL_PATHS
Extra skill directories (colon-separated)
—
DCC_MCP_SKILL_PATHS
Global extra skill directories
—
Bridge Protocol
The Python ↔ Photoshop communication goes through the adobepy Rust broker using the adobepy protocol (v0.2.0). The broker handles JSON-RPC 2.0 routing, session management, and timeout control.
from adobe.dcc_mcp import action_result
from adobe.photoshop import Photoshop
from dcc_mcp_core.skill import skill_entry
@skill_entry
def list_layers(**kwargs) -> dict:
"""List all layers in the active Photoshop document."""
app = Photoshop()
return action_result(
"Listed active Photoshop layers",
lambda: {"layers": [layer.name for layer in app.activeLayers]},
prompt="Use the layer names in the next Photoshop operation.",
)
def main(**kwargs):
return list_layers(**kwargs)
if __name__ == "__main__":
from dcc_mcp_core.skill import run_main
run_main(main)
dcc-mcp-photoshop [OPTIONS]
Options:
--mcp-port PORT Optional fixed MCP instance port (default: OS-assigned)
--broker-url URL adobepy broker URL (default: http://127.0.0.1:47391)
--gateway-port PORT Gateway competition port
--server-name NAME Server name in MCP initialize (default: photoshop-mcp)
--skill-paths PATH Extra skill directories
--no-builtins Do not discover built-in skills
--verbose, -v Enable debug logging
--version Show version and exit
Python API
import dcc_mcp_photoshop
handle = dcc_mcp_photoshop.start_server(broker_url="http://127.0.0.1:47391")
print(f"MCP URL: {handle.mcp_url()}")
# ... use with Claude Desktop, Cursor, etc.
handle.shutdown()
The UXP bridge template is part of adobepy, while the canonical lifecycle owns
its safe generation and receipt:
dcc-mcp-photoshop install --json --yes
This stages receipt-owned bridge files only. The canonical agent lifecycle does
not automate UXP Developer Tool or treat an adobepy doctor call as installation
progress. It remains fail-closed until the bounded Photoshop bootstrap/load
contract in dcc-mcp/adobepy#67 is available, then continues with
dcc-mcp-photoshop verify --json.
For human-controlled development only, outside the Install SOP readiness claim:
Open Photoshop
Go to Plugins → Development → Load Plugin...
Navigate to adobepy's bridges/uxp/photoshop/ and select manifest.json
Bridge manifest
The bridge manifest is at bridges/uxp/photoshop/manifest.json in the adobepy repository:
Adobe Photoshop MCP adapter for AI agents to edit documents, layers, text and images through the shared adobepy UXP bridge and typed tools in the DCC-MCP ecosystem.
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Preguntas
¿Cómo instalo Dcc MCP Photoshop?
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
¿Dcc MCP Photoshop necesita una clave de API?
Este registro no indica ninguna variable de entorno obligatoria.
¿Qué transporte usa Dcc MCP Photoshop?
Dcc MCP Photoshop se ejecuta localmente por stdio.
¿Cuándo se comprobó Dcc MCP Photoshop por última vez?
Última comprobación: 2026-11-05. Adobe Photoshop MCP adapter for AI agents to edit documents, layers, text and images through the shared adobepy UXP bridge and typed tools in the DCC-MCP ecosystem.