Skip to content
Beta2D & Texture

MCP for Photoshop — Connect AI Agents to Photoshop

Texture work is a naming and color-management problem before it is a visual one. Agents get tools that keep layer stacks editable and export maps your engine will actually accept.

Install Photoshop integrationComing soon
Read-only by default9 typed toolsCheckpointed writes
Technical specification
Host software
Photoshop 2024, 2025 and 2026
Runtime
UXP plugin (JavaScript) with an ExtendScript fallback for legacy actions
Transport
stdio (local) and streamable HTTP (studio)
Install
UXP plugin + npx dccmcp-photoshop
Documents
PSD, PSB, TIFF, PNG, JPEG, EXR (via host support)
Platforms
Windows, macOS
Last reviewed
2026-09-14
Overview

What is MCP for Photoshop?

MCP for Photoshop is a local MCP server plus a Photoshop plugin that connects AI agents to a real Photoshop session. Agents discover 9 typed tools — including document.inspect, layer.create, layer.effects and mask.create — and call them to inspect, create, modify and validate work inside the live application.

Unlike generated Photoshop scripts, every call is validated against your current document, classified as read, write or execute, and recorded in an audit log. Photoshop stays open, the document stays live, and destructive operations are checkpointed so they can be rolled back.

It works with Claude Code, Codex, Cursor, GitHub Copilot, Claude Desktop, Gemini CLI, Trae, Doubao, Qwen Code, CodeBuddy, Custom MCP clients over stdio or streamable HTTP.

  • Host software: Photoshop 2024, 2025 and 2026
  • Runtime: UXP plugin (JavaScript) with an ExtendScript fallback for legacy actions
  • Transport: stdio (local) and streamable HTTP (studio)
Why it breaks

What goes wrong when agents drive Photoshop without a contract

01

Automation flattens the file it was meant to speed up

Batch scripts that flatten layers to export a PNG destroy the source PSD's editability. The artist pays for that automation for months.

02

Texture maps arrive in the wrong color space

Normal and roughness maps must not be sRGB-encoded, yet exports that ignore document profile produce maps that subtly break lighting in engine.

03

Naming conventions are the whole pipeline

A map called final_v2_NORMAL_fixed.png breaks the import. Engines want deterministic suffixes, consistent sizes and predictable channel packing.

How it works

How MCP for Photoshop keeps intent, structure and traceability intact

An MCP server and Photoshop UXP plugin that exposes documents, layers, masks, adjustment stacks, channel and profile state and batch export as typed tools for texture and marketing pipelines.

Non-destructive by default

Edits land as layers, masks and adjustment layers. Flattening, merging and destructive filters require an explicit policy approval.

Color-managed export

The agent declares the target color space per map type, and the server validates document profile and bit depth before writing the file.

Tokenized texture sets

Export a full PBR set — base color, normal, roughness, metallic, AO, height — with a naming template and consistent resolution, then write a manifest.

Checkpointed documents

A versioned checkpoint is written before mutating operations, so a bad batch can be rolled back per document rather than per folder.

Tool reference

MCP for Photoshop tools — every tool and its risk class

Agents discover this list at connect time. You decide which entries are auto-approved, which need a human and which are denied in production files.
  • document.inspectSize, resolution, color mode, profile, bit depth and layer tree.read
  • layer.createCreate pixel, fill, shape, text, group or adjustment layers in place.write
  • layer.effectsApply layer styles, blend modes, opacity and clipping relationships.write
  • mask.createBuild layer and vector masks from selections, channels or alpha sources.write
  • selection.modifyGrow, feather, invert, refine and save selections into channels.write
  • adjustment.applyApply non-destructive adjustment layers with validated parameters.write
  • batch.actionRun approved actions across a document set with per-file result reporting.execute
  • texture.export_setExport a tokenized PBR map set with color-space validation and a manifest.execute
  • asset.exportExport flattened or layered output at declared sizes and formats.execute
Install

Install MCP for Photoshop in four steps

Everything runs locally. The server binds to loopback by default and only exposes the tools you approve in Photoshop.

Pre-release. These commands describe the interface we are shipping for MCP for Photoshop — the packages are not published yet. Get notified when MCP for Photoshop launches.

STEP 01

Install the UXP plugin

Install the DCCMCP plugin through the UXP Developer Tool or your studio's extension deployment.

uxp install ./dccmcp-photoshop.ccx
STEP 02

Start the bridge

The bridge connects your MCP client to the running Photoshop instance and its open documents.

npx dccmcp-photoshop@latest serve --session active
STEP 03

Register the client

Register the server with Claude Code, Codex, Cursor, OpenClaw or any other MCP-compatible client.

{
  "mcpServers": {
    "photoshop": { "command": "npx", "args": ["dccmcp-photoshop", "serve"] }
  }
}
STEP 04

Declare your map convention

Tell the server which suffixes and color spaces your engine expects so exports are validated against them.

dccmcp texture set --template "{name}_{map}_{res}.png" --linear normal,roughness,metallic,ao,height

MCP for Photoshop works with the agents you already use

  • Claude Code
  • Codex
  • Cursor
  • GitHub Copilot
  • Claude Desktop
  • Gemini CLI
  • Trae
  • Doubao
  • Qwen Code
  • CodeBuddy
  • Custom MCP clients

Any other MCP-compatible client works too — one config entry, stdio by default.

Read the docs
Also available

Other MCP integrations that pair with Photoshop

MCP for Blender

Connect AI agents to Blender — scene graph, geometry nodes, renders and batch automation.

View integration

MCP for Rhino

Drive Rhino and Grasshopper from an AI agent — NURBS, layers, blocks and parametric definitions.

View integration

MCP for FreeCAD

Parametric CAD automation for agents — sketches, features, tech drawings and STEP exports.

View integration

10 integrations available

Compare tool lists, support matrices and policies for every supported application.

Browse all integrations
FAQ

Questions teams ask before they install

If something is missing, ask us directly — we answer technical questions with technical answers.

  • No. The integration does not invoke Firefly or any generative feature. It exposes document, layer, mask, color-management and export operations only, so your files are never sent to a generative model through us.

  • Not unless a policy allows it. Edits are made with layers, masks and adjustment layers, and destructive operations such as flatten or merge are denied by default.

  • Photoshop 2024, 2025 and 2026, using the UXP plugin architecture. Legacy ExtendScript actions can still be run through the batch tool for compatibility.

  • Yes. The texture export tool writes a full map set with your naming template, validates linear versus color data per map type, and produces a manifest listing every file it wrote at what resolution.

  • No. DCCMCP is an independent third-party integration and is not affiliated with, endorsed by or sponsored by Adobe.

npx dccmcp-blender@latest serve

Put an agent inside your real tools — without putting your pipeline at risk

Install an integration, set a policy, and let your agent inspect, build and validate work in Blender, Maya, Houdini, 3ds Max, Rhino, ZBrush, Photoshop, FreeCAD, QGIS or OpenCV. Free to start, local by default.

Coming soonRead the quickstart

macOS · Windows · Linux — no cloud dependency required