Suite coordinator
The Suite coordinator joins app servers behind two explicit cross-app workflows: placing Illustrator artwork in InDesign and copying supported Illustrator swatches into InDesign.
What this implementation covers
Workflow: place an artboard from the active Illustrator document on an InDesign page as a linked .ai file; copy supported RGB/CMYK process, spot and gray swatches while preserving InDesign built-ins. Gradients and patterns are reported, not copied.
For feature-level detail and evidence, see the Capability Atlas.
Connection and requirements
How it reaches the app
Starts standalone MCP server implementations as local child processes and delegates workflow steps through MCP. It speaks MCP over stdio to the client.
What you need
Node.js 18+ and InDesign plus Illustrator for its current workflows. Other child apps can be selected, but that does not add coordinator workflows.
Package: adobe-mcp-suite. Add it as a local stdio MCP server using CLI & client configuration.
API and content conventions
The coordinator advertises its own workflow tools only; it does not mirror child tool inventories. Install standalone app servers for direct app tools. Use its package README for delegation semantics and constraints.
Discover the running package’s exact tool names and JSON input schemas through MCP tools/list. If the server provides help, use it to inspect a tool or category. Schemas from a different package version may not match.
Target and units: Select child app IDs with --apps or ADOBE_MCP_APPS. Current workflows need both InDesign and Illustrator. File permissions remain app-specific: configure both participating app servers as needed.
CLI and configuration
This package is launched as a persistent MCP process, not as a conventional one-shot CLI. Relevant settings documented by the package include:
ADOBE_MCP_APPS plus per-app variables documented by each child package; the coordinator forwards matching variables rather than acting as a single app backend.
Variable names and defaults are package-specific; consult the package README before changing them. File-operation permissions and bridge tokens should be configured in the client’s environment, not embedded in prompts or checked into source.
claude mcp add suite -- npx -y adobe-mcp-suiteWith Homebrew, the coordinator and every app server are installed on your PATH:
brew tap zachshallbetter/tap
brew trust zachshallbetter/tap
brew install zachshallbetter/tap/adobe-mcp
claude mcp add suite -- adobe-mcp-suiteFor client-neutral JSON configuration and source-checkout commands, see CLI & configuration.
Full reference
The repository README is maintained alongside this implementation and covers exact setup, tool families, package-specific behavior, limitations, security and development status.