agentleFS
nutriandreanutriandrea/adobe-indesign-mcp/skills/indesign/indesign-mcp-layout/SKILL.md

indesign-mcp-layout

Skill41 starsChanged 4 months agoMITView on GitHub

Use when driving Adobe InDesign through this MCP server. Prefer the typed tools; read before using export_executeScript or script_run.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Confirm the target document: before mutating. Call document_getState first, then pass the document's name (or its activeDocumentIndex) as …

    line 43
  2. Very specific:

    Prefer text_getContent / grep_find to read state before writing it.

    line 48
  3. Very specific:

    Use document_listOpen when you want the answer through a tool call.

    line 61
  4. Very specific:

    Read before you write. text_getContent returns frame contents, and text_getFormatting returns the per-range font, size and character style …

    line 65

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

InDesign Layout Through MCP

This server exposes typed tools with bare snake_case names — document_create, text_addFrame, table_setCell and 194 more. They validate their arguments, wrap ExtendScript internally and apply timeouts and error handling. Use the typed tools. Raw script execution is a last resort.

Why typed tools instead of raw ExtendScript

export_executeScript / script_run push code straight to the InDesign bridge. There is no cancellation: if a script hangs inside InDesign, the host process stays busy and every later tool call queues behind it until the host is restarted. Never use raw scripts for loops, font enumeration, multi-mutation probes, or anything that touches many DOM objects.

Instead of raw ExtendScriptUse
Read document infodocument_getInfo
Enumerate fontsfont_list (per-frame details: text_getFormatting)
Create a documentdocument_create
Add pagespage_add
Create a text frametext_addFrame
Create shapesshape_rectangle_create / shape_ellipse_create / shape_polygon_create
Create colorscolor_swatch_create
Build or edit tablestable_create / table_setCell / table_setRowColumnSize
Search and replace textgrep_replace / text_findReplace
Create stylesstyle_createParagraph / style_createCharacter
Apply styles to texttext_applyParagraphStyle / text_applyFont
Read text contenttext_getContent / text_getFormatting
Exportexport_document
Check the connectiondocument_listOpen — or read the mcp://bridge/status resource

Before any layout task

  1. InDesign must be open and visible. With no open document the calls fail, and on the Windows COM bridge a non-visible instance leaves the user looking at an empty application.
  2. Confirm the target document before mutating. Call document_getState first, then pass the document's name (or its activeDocumentIndex) as document_id on the calls that follow — every tool accepts it. With no document_id a tool acts on the front document, so with more than one document open the wrong front tab is a common failure.
  3. Prefer text_getContent / grep_find to read state before writing it.

Resources

Besides the tools, the server exposes read-only resources for cheap checks. They never touch InDesign and cost no round-trip, so they are the right way to answer "is this thing alive?":

  • mcp://bridge/status — is the bridge reachable, and how deep is the queue
  • mcp://session/status — this session's state
  • mcp://document/active — the front document's cached state
  • mcp://tools/inventory — the full tool list, for discovery

Use document_listOpen when you want the answer through a tool call.

Reading state

Read before you write. text_getContent returns frame contents, and text_getFormatting returns the per-range font, size and character style — enough to decide what to change without executing a probe script.

Windows / COM notes

The Windows bridge talks to InDesign over COM, which differs from the macOS UXP/JXA path in a few places worth knowing:

  • Dialogs must not appear. Scripts run with app.scriptPreferences.userInteractionLevel set to NEVER_INTERACT, so export and font dialogs cannot block on Windows.
  • Some font properties throw. In raw ExtendScript, fontFamily, italic and weight are not supported and raise an error. Use appliedFont, which returns "Family\tStyle", plus fontStyle. Variable fonts are reported as tab-separated names such as "Fraunces\tMedium".
  • Enums are read-only. ColorModel members are ColorModel.PROCESS (and friends); assigning to them throws "ColorModel is read only". Read the enum value instead of assigning it.

Geometry gotchas

  • Bounds are [top, left, bottom, right], and they must be well formed: an inverted or degenerate rectangle throws.
  • InDesign 2026 rejects re-anchoring an object with move() when the target is an insertion point. The typed anchored-object tools add the object to the insertion point's own collection instead.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.