All stories
InDesign Nutria MCP Ecosystem Developing

InDesign MCP lets AI agents target a document instead of guessing the front tab

The community server's v1.5.0 release adds an optional document_id to tool calls, with an error when the requested document is not open.

Sources (5)

Why now The October 18 release addresses a concrete failure in multi-document publishing workflows, where an agent could otherwise modify whichever InDesign tab happened to be in front.

An AI agent editing an InDesign brochure should not accidentally change the catalog in the next tab. InDesign Nutria MCP’s October 18 v1.5.0 release addresses that problem with an optional document_id argument: the host can name an open document, or supply its zero-based index, instead of relying on the frontmost document.

The maintainer says every tool now accepts the argument and document-scoped handlers use a shared resolver. If the named document is not open, the call fails with the list of open documents instead of silently falling back to the front tab. Omitting the argument preserves the old front-document behavior, so this is an explicit targeting mechanism rather than an automatic guarantee against every wrong-file edit.

A specific target for a live publishing application

The documented workflow is to inspect the document state, obtain the name reported by document_listOpen, and pass the target on subsequent calls. The release also says each call carries its own target through asynchronous execution, keeping overlapping requests from borrowing another call’s document selection.

InDesign Nutria MCP is an independent, MIT-licensed community server, not an Adobe release or a new model. Claude Desktop, OpenCode or another compatible MCP host launches the local Node.js server over stdio. Its tools can create layouts, change text and styles, place images, save documents and export files inside a local InDesign installation.

Installation currently means cloning the repository, running npm install and npm run build, then launching node dist/index.js; the project explicitly says it is not published to npm. It requires Node.js 18 or later and lists InDesign 2022 or newer. A UXP panel connects the application on macOS or Windows; alternative bridges use JXA on macOS or an opt-in COM connection on Windows.

Platform checks and permissions still matter

The maintainer reports an end-to-end check against InDesign 2026 version 21.3 using the plugin-free macOS path. The Windows guide explicitly describes its COM path as shipped but not exercised against a live Windows InDesign instance by the maintainer. Those are different levels of validation, and AITrending has not independently run the integration.

The server drives an application that can modify local publishing files. Its documentation says custom script tools have no cancellation, and document_close defaults to closing without saving; save explicitly before closing. The MCP host supplies the model account, while InDesign and any model usage remain separate requirements. The sources do not establish an all-inclusive usage price.

For teams already connecting an agent to InDesign, the new hook is straightforward: target the intended document on every relevant call, rather than treating the active tab as reliable task context.