HN Showcase
Back to browse
GitHub Repository
50 starsJavaScript

InDesign MCP via UXP plugin – faster, cross-platform, no AppleScript

by theloniuser·Mar 1, 2026·1 point·0 comments
Visit ProjectView on HN

AI Analysis

●●SolidBig BrainSolve My Problem

Replaces flaky AppleScript automation with native UXP plugin; adds Windows support and structured JSON returns.

Strengths
  • •Cross-platform (macOS + Windows) vs AppleScript macOS-only; direct in-process execution eliminates temp file overhead
  • •Modern JavaScript (async/await, destructuring) inside InDesign vs deprecated ExtendScript (ES3 only)
  • •~130 tools covering full InDesign API — documents, pages, text, graphics, styles, exports — comprehensive feature coverage
Weaknesses
  • •Requires InDesign 2024+; older versions unsupported, limiting adoption in enterprises on older releases
  • •MCP is still emerging ecosystem; depends on adoption of MCP clients (Claude, others) for real utility
Target Audience

AI developers building InDesign automation; InDesign power users integrating with Claude or other MCP clients

Similar To

zachshallbetter/indesign-mcp-server (original AppleScript version) · Cursor InDesign extension · ExtendScript-based automation tools

Similar Projects

Developer Tools●●Solid

CasperAI – A local MCP server for cross-platform engineering context

It stitches Slack threads, PRs, tickets and docs into a local "context lake" and can point a mention like handlePayment() straight to the file and related PRs — very practical for debugging and postmortems. The use of SQLite FTS5 for local full-text search plus MCP for a unified context layer is a smart, pragmatic combo; success will hinge on connector reliability and search/ranking quality, not the README.

Niche GemSolve My Problem
chose166
113mo ago
Developer Tools●●Solid

CasperAI – A local MCP server for cross-platform engineering context

It builds a local 'context lake' (SQLite + FTS5) that stitches Slack threads, PRs, tickets and docs to precise code locations so queries like "Why did the payment service deploy fail last week?" return linked commits, messages and files. The local-first approach is a sensible privacy + reliability choice and the bi-directional linking of mentions to file:line is the clearest practical win here. That said, the idea sits in a crowded space—quality of connectors and ranking will determine whether this is indispensable or just another repo-chat tool.

Niche GemShip It
chose166
103mo ago