adobe-mcp

MCP servers for Adobe applications. Each application has its own server you
can install on its own; a suite that combines them into one server is on the
way.

Each server runs on the machine where the Adobe application is installed and
talks to it through ExtendScript, the scripting interface the applications ship
with. macOS and Windows are supported.

Install one application

Claude Code:

claude mcp add indesign -- npx -y indesign-mcp-server

claude mcp add illustrator -- npx -y adobe-mcp-illustrator

Any client that reads an mcpServers block:

{
  "mcpServers": {
    "indesign": { "command": "npx", "args": ["-y", "indesign-mcp-server"] },
    "illustrator": { "command": "npx", "args": ["-y", "adobe-mcp-illustrator"] }
  }
}

Each package's README covers its tools, conventions and configuration.

How the repository is organised

packages/
  core/          adobe-mcp-core           shared by every server
  indesign/      indesign-mcp-server
  illustrator/   adobe-mcp-illustrator

The servers share their infrastructure through adobe-mcp-core, so a fix to
escaping, path checks, result handling or the script runner reaches every
server. What differs between applications stays in each package: its tools,
its instructions, and how the application is told to run a script.

Development

npm install      # installs every package and links them together
npm run check    # syntax check, every package
npm test         # every package's tests, including each server's static script audit

Run one package's tests with npm test -w packages/illustrator. The static
audits run every tool against a stubbed application and check each generated
script against the application's scripting object model; they do not need
InDesign or Illustrator installed.

See CONTRIBUTING.md for releasing and for each package's guide.

Licence

MIT. See each package's LICENSE.