Skip to main content
Glama
gavricci

artwork-preflight-mcp

by gavricci

Related Servers

Alternatives to artwork-preflight-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables programmatic document proofing for print, with real ink coverage measurement and waste page detection, letting agents decide what to print before any sheet is produced.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to inspect generated .docx and .pdf files before delivery, extracting structural, typographic, spacing, and language facts so formatting errors can be caught automatically.
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to inspect, modify, export, and validate design documents with 47 tools covering design, code generation, branding, and print/mockup workflows.
      1 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to diff inventory snapshots from CSV files or live Shopify stores, surfacing SKU mismatches, oversell risks, blank-vs-zero issues, barcode conflicts, and sync health, with data processed locally.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server for in-loop design review of web previews. It enables agents to submit a preview URL, receive structured findings with suggested fixes, and recheck after applying changes, while never editing code itself.
      5
      1
      MIT

    TDQS

    A4.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues