Idml Mcp

io.github.jimprivatePublished by GitHub account jimprivatev0.1.1Updated Oct 27, 2026

MCP server for AI agents to read and safely edit Adobe InDesign IDML files. No InDesign required.

VerifiedSTDIODesktop onlyFiles & StorageMedia & Design

Overview

AI-generated overview

Local MCP server that lets an AI assistant read, summarize and safely edit Adobe InDesign IDML files without InDesign installed.

What you can do
  • Summarize an IDML package into pages, frames, stories, image links and styles
  • Read a single story's plain text with indexed, styled text runs
  • Replace one text run's content while leaving layout and XML byte-for-byte intact
  • Repoint an image link to a different file without changing geometry
When to use it
Useful for template-driven publishing, localization and agent pipelines that need to read a designed layout and apply targeted text or image updates to IDML files, on machines or CI where Adobe InDesign is not available.
Requirements
Runs as a local stdio process started with Node.js (npm package idml-mcp); the README configures it by pointing the command at the built server.js file. No authentication, environment variables or headers are declared. Desktop only.
Before you install
It writes IDML files: text replacement and image relinking modify document content, so work on copies and keep backups. The README claims byte-for-byte preservation of everything else, but that is the vendor's own claim. No credentials or network access are requested.

Installation

In SourceWeft

  1. Open Idml Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

idmlkit

The AI-native toolkit for Adobe InDesign files (IDML) — parse, summarize, and safely write back. No InDesign required.

AI tools have transformed how we write code and build web pages, but print and layout designers have largely been left out: the InDesign ecosystem has no AI-ready open interface. Existing InDesign MCP servers all remote-control a running InDesign instance — which means a license, a desktop, and an open app for every operation.

idmlkit takes the other road: it works directly on .idml files (InDesign's open, XML-based interchange format). That means it runs anywhere Node.js runs — servers, CI pipelines, Linux, a designer's laptop — with nothing from Adobe installed.

JSON data in ──► idmlkit ──► perfectly laid-out IDML out ──► open in InDesign / print

Design philosophy: the AI never touches the XML

LLMs are great at understanding a document and deciding what should change, and terrible at hand-editing 5,000 lines of layout XML without breaking it. So idmlkit splits the work:

  • Deterministic code parses the package and produces a compact, LLM-friendly summary (pages, frames, stories as indexed text runs, image links, styles) — a few hundred tokens instead of megabytes of XML.
  • Write-back is surgical: replacing a text run or relinking an image rewrites only that one element via targeted string surgery. Everything else — geometry, styles, the XML formatting itself — is preserved byte-for-byte (enforced by tests). The AI physically cannot corrupt your layout.

Validated against real InDesign 2025 exports: on Adobe's official Flex Layout sample (14.5 MB, with a single 20 MB spread), summarize runs in under half a second and a text edit changes exactly one zip entry — every other entry verified byte-identical by CRC.

Packages

PackageWhat it is
idmlkitCore library + CLI: open, summarize, safe text/image write-back
idml-mcpMCP server exposing those abilities to Claude and any MCP-capable agent

Quick start

sh
npm installnpm run buildnode scripts/make-sample-idml.mjs   # generates examples/sample.idml

CLI

sh
$ node packages/idmlkit/dist/cli.js summary examples/sample.idmlPages: 1  Spreads: 1Story u123 (11 words, 2 runs): Spring Catalog 2026 Fresh arrivals for the new season…Image link u202: file:/images/hero.jpgParagraph styles: $ID/NormalParagraphStyle, Headline, Body
$ node packages/idmlkit/dist/cli.js set-text examples/sample.idml u123 0 "Summer Sale 2026" -o out.idml$ node packages/idmlkit/dist/cli.js relink out.idml u202 "file:/images/summer.jpg"

MCP server (Claude Code / Claude Desktop)

json
{  "mcpServers": {    "idml": {      "command": "node",      "args": ["<repo>/packages/idml-mcp/dist/server.js"]    }  }}

Then ask Claude things like "Summarize catalog.idml and replace every 2025 date with 2026" — it will use these tools:

ToolPurpose
idml_summarizeStructured summary of pages, frames, stories, images, styles
idml_get_storyOne story's plain text + indexed runs with styles
idml_set_textReplace one run's text (layout untouched, byte-for-byte)
idml_relink_imagePoint an image link at a new file (geometry untouched)

Library

ts
import { IdmlDocument, summarizeDocument, setStoryRunText } from "idmlkit";
const doc = await IdmlDocument.open("catalog.idml");console.log(summarizeDocument(doc));      // LLM-friendly JSONsetStoryRunText(doc, "u123", 0, "New headline");await doc.save("catalog-updated.idml");

Use cases

  • Database publishing: fill a designed template with product data — thousands of catalog pages, price lists, or menus without opening InDesign once.
  • Localization: extract every text run with its styles, translate, write back safely.
  • Agent workflows: let Claude read a layout, reason about its content, and apply text/image updates as part of a larger pipeline.

Roadmap

  • Read IDML packages, LLM-friendly summaries
  • Safe text run replacement and image relinking
  • MCP server (stdio)
  • Page → frame mapping with geometry (which frame is where)
  • Template fill: apply a JSON data object to a tagged template in one call
  • Story-level structured diff (what changed between two IDML files)
  • Overflow heuristics (warn when new text likely won't fit its frame)
  • Real-world IDML corpus tests (CC 2018–2026 exports)

Development

sh
npm installnpm run build     # tsc project referencesnpm test          # vitest — includes byte-for-byte preservation tests

License

MIT. Not affiliated with or endorsed by Adobe. "Adobe" and "InDesign" are trademarks of Adobe Inc., used here only to describe compatibility.

Source: README.md at commit 0d781d4

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts