indesign-cli MCP Server
Related Servers
Alternatives to indesign-cli MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceEnables AI assistants to control Adobe InDesign for automated publishing workflows, document creation, and layout tasks across macOS and Windows.361MIT
- AlicenseCqualityBmaintenanceEnables AI assistants to automate Adobe InDesign publishing workflows, including document creation, text formatting, image placement, PDF export, and more via 35+ professional tools.3636MIT
- FlicenseNot gradedqualityAmaintenanceEnables Claude to create and edit Adobe InDesign documents, including pages, text frames, styles, images, and previews.10-
- AlicenseBqualityAmaintenanceEnables AI assistants to control Adobe InDesign on Windows via the Model Context Protocol, allowing document inspection, text and style editing, and exports to formats like PDF, images, and EPUB.1912MIT
- AlicenseCqualityCmaintenanceTransforms Adobe InDesign into an AI-powered design automation platform with 135+ professional tools for seamless programmatic control over layout and design capabilities.10020MIT
- AlicenseCqualityBmaintenanceA Model Context Protocol (MCP) server that gives AI assistants direct, native control over Adobe InDesign via a UXP plugin bridge, with ~130 tools covering documents, pages, text, graphics, styles, master spreads, books, and export.10093MIT
TDQS
Scored across 114 tools
Several tool pairs have overlapping boundaries: get_document_layers/list_layers, get_document_styles/list_styles, get_document_colors/list_color_swatches, and reframe_page/resize_page appear to target the same resource/action. The get_document_info/get_session_info/view_document trio also creates ambiguity, making it hard for an agent to reliably select the intended tool.
Most tools follow a consistent snake_case verb_noun pattern such as create_, get_, set_, delete_, and export_. Minor deviations exist though: equivalent listing operations are split between get_document_* and list_* names, and find_replace_text doesn't match the pattern of find_text_in_document.
With 114 tools, this server presents an extreme mismatch for a typical MCP surface, far exceeding the 50+ tool threshold. Even for a complex application like InDesign, the sheer number creates significant selection overhead and makes the toolset difficult for agents to navigate effectively.
The server covers a broad range of document, page, spread, item, and style operations, but lifecycle coverage is uneven. Colors, hyperlinks, sections, and styles can typically be created and queried but not updated or deleted, leaving clear dead ends in several workflows.