Creative MCP
Implementation guide · InDesign

InDesign

The InDesign MCP server controls documents, pages and spreads, typography, tables, styles, images and links, long-document workflows, interactive output, prepress and export.

What this implementation covers

documents; pages, spreads and parent pages; text, stories and tables; typography and styles; images, links and color; books, indexing and cross-references; data merge; prepress and export; preferences and scripting.

For feature-level detail and evidence, see the Capability Atlas.

Connection and requirements

Runtime route

How it reaches the app

ExtendScript via AppleScript on macOS or COM through PowerShell on Windows. Optional UXP bridge backends are described in the package guide.

Prerequisites

What you need

InDesign 2023 or later recommended; Node.js 18+; macOS or Windows.

Package: adobe-mcp-indesign. Add it as a local stdio MCP server using CLI & client configuration.

API and content conventions

Use MCP help to inspect tools by category and exact arguments. A generated tool reference lives in the package docs. The package also includes optional UXP backend and bridge setup.

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: Measurements in the main tool set are commonly millimetres. Verify each tool description; object indices and units are tool-specific. File paths stay under the home folder plus INDESIGN_ALLOWED_DIRS.

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:

INDESIGN_APP_NAME, INDESIGN_BACKEND, INDESIGN_SCRIPT_TIMEOUT_MS, INDESIGN_ALLOWED_DIRS, INDESIGN_TARGET; optional UXP bridge settings.

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 indesign -- npx -y adobe-mcp-indesign

For 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.