idmly-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IDMLY_OUT_DIR | No | Default output directory. Default: next to the source. | |
| IDMLY_ENGINE_URL | No | Override for a self-hosted engine. Default: the hosted engine. | |
| IDMLY_LICENSE_KEY | No | Your license key from idmly.com. Default: none (free trial). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_to_indesignA | Convert a self-contained HTML design into an editable Adobe InDesign IDML file and write it to disk. Provide exactly one of: html (the full document as a string), path (a local .html file; only that one file is uploaded, so inline its CSS, fonts and images first), or url (a public link to a hosted .html). Returns the output path plus pages converted, fonts InDesign needs active, and a geometry check. Designs with images come back as an .idml next to a Links/ folder; keep them together. Without a license key only the first pages convert (free trial) and the result includes the purchase link. |
| idmly_statusA | Check that the idmly engine is reachable and whether a license key is configured for this MCP server (presence only; the key is validated on conversion). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one performs the HTML-to-IDML conversion, the other only reports engine reachability and license presence. There is no plausible overlap or misselection risk between them.
Both names use snake_case, which is consistent, but the verb_noun pattern in 'convert_to_indesign' is not mirrored by 'idmly_status', which is a service-prefixed noun phrase. The deviation is minor and still clearly readable.
Two tools is on the thin side, but the server has a single narrow purpose (converting HTML into IDML) plus a health check, so each tool earns its place. There is little room to add tools without inventing scope.
The surface covers the core workflow (convert from html/path/url, inspect status) and returns useful diagnostics like fonts and geometry. Gaps such as batch conversion, job polling, or reverse IDML-to-HTML export are noticeable but not blocking for the stated purpose.