Adobe MCP Suite GitHub

Open source / Local automation

MCP servers for your Adobe apps.

Connect your Model Context Protocol client to seven Adobe creative applications. Install the apps you need and run their tools through a local bridge.

Get the installer Explore the apps

Free under MIT No API key or cloud backend

Independent app servers
07
Tools enabled by default
131
Transport
Local stdio

01 / Applications

Seven apps. Seven tool sets.

Each app has its own server, tool catalog, and connection. Pick what fits your workflow.

20 tools

Premiere Pro

Inspect sequences, add markers, relink media, and prepare exports.

Premiere Pro tools
20 tools

Photoshop

Edit document layers and text, crop and resize images, and export results.

Photoshop tools
15 tools

Media Encoder

Read source metadata, queue media and image sequences, and manage batches.

Media Encoder tools
21 tools

Illustrator

Work with artboards, layers, shapes, and linked images. Export SVG, PNG, or PDF.

Illustrator tools
19 tools

InDesign

Manage pages, text frames, and linked assets. Save or export INDD, PDF, and IDML.

InDesign tools
25 tools

After Effects

Inspect compositions, adjust layer timing, edit keyframes, and set render templates.

After Effects tools
11 tools

Audition

Discover host commands, run command batches, and inspect or navigate waveform documents.

Audition tools

02 / Quick start

Set up from your terminal.

The portable ZIP includes Node.js and its dependencies. Choose Premiere Pro and Photoshop below, or use --apps all.

  1. Download and verify

    Get your platform ZIP from GitHub Releases, compare its SHA-256 hash with SHA256SUMS, then extract it.

  2. Choose your applications

    Run the command for your system from the extracted folder. On Windows or macOS, restart Adobe and open the suite's CEP panel.

  3. Connect your MCP client

    Import the generated mcp-servers.json. Use adobe-mcp doctor --live while the servers run to check their connections.

INSTALL COMMAND
Operating system 
.\adobe-mcp.cmd install --apps pr,ps --enable-unsigned

Windows x64 · CEP panels

chmod +x ./adobe-mcp ./runtime/node
./adobe-mcp install --apps pr,ps --enable-unsigned

Intel and Apple Silicon · CEP panels

chmod +x ./adobe-mcp ./runtime/node
./adobe-mcp install --apps pr,ps --server-only

x64 and ARM64 · MCP discovery only; no native Adobe host

Full installation guide

Check CEP compatibility first. On Windows and macOS, --enable-unsigned enables unsigned development panels for your user account. Native workflows have not yet been verified inside Adobe applications. This project uses CEP/ExtendScript and does not include a UXP adapter.

03 / Behind the tools

Local by design.

An MCP client launches each selected server over stdio. The server talks to its Adobe panel over an authenticated loopback connection. Every server also provides discovery resources and prompts that work with the panel disconnected.

Read the architecture notes

Updates on your terms

The manager checks for stable releases and prints a notice when one is available. Run adobe-mcp update when ready, or use adobe-mcp rollback to return to the previous installed version.

Browse terminal commands