artwork-preflight-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PREFLIGHT_ROOT | No | Base directory for resolving all file paths. Defaults to the current working directory. | current directory |
| PREFLIGHT_SCOPES | No | Comma-separated list of tool scopes to register (e.g. 'inspect,check,fix'). Defaults to all available scopes. | all |
| PREFLIGHT_AUDIT_LOG | No | Path to a JSONL file where one line is appended per tool call. If unset, no audit log is written. |
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 |
|---|---|
| inspect_artworkA | Read the technical properties of an artwork file: pixel size, declared resolution, colour space, ICC profile, transparency and where the visible content sits. Reports what the file says; makes no judgement about whether it can be printed. |
| check_print_readinessA | Check an artwork file against a print product and return every problem found, each with a severity. Errors block printing; warnings are things the customer should know before approving a proof. |
| list_presetsA | List the print products this server knows how to check, with their physical requirements. |
| suggest_fixesA | Turn the problems found in an artwork file into concrete actions - one message written for the customer and one for whoever handles the job internally. Suggests only; it never modifies the file. |
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 4 tools
Each tool has a clearly distinct role: inspect_artwork reads raw file properties, check_print_readiness validates against a product, list_presets enumerates available products, and suggest_fixes generates recommendations. There is no overlap or ambiguity between them.
All four tool names follow a consistent verb_noun pattern: inspect_artwork, check_print_readiness, list_presets, suggest_fixes. The naming convention is uniform and predictable.
With four tools, the server is tightly scoped to the preflight workflow. Each tool earns its place, covering the essential operations without unnecessary bloat or missing coverage.
The domain is artwork preflight, and the set covers the full workflow: inspect raw properties, check against a specific product, discover available products, and get recommended fixes. There are no obvious dead ends or missing operations for a non-mutating preflight service.