Skip to main content
Glama
Bieuulls

Illustrator AI & MCP Control

by Bieuulls
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Illustrator AI & MCP Control

No user-submitted related servers found.

    Related Servers

    • Illustrator MCP

      jinkeda
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that lets AI assistants like Claude control Adobe Illustrator through natural language by executing ExtendScript code and providing document state inspection.
      12
      7
      MIT

    • Illustrator AI MCP Server

      Gokul2
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that lets AI assistants control Adobe Illustrator locally—running ExtendScript, capturing canvas screenshots, exporting artwork, and optionally remembering techniques—all without network activity.
      -

    • Adobe MCP

      gauravvvvvvvvvv
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to drive Adobe creative applications such as Premiere Pro, After Effects, Photoshop and Illustrator through a compact, state-aware interface with capability search and semantic execute or batch_execute calls. A localhost WebSocket bridge keeps host adapters auto-reconnecting, so applications can be opened, closed or swapped without restarting the server.
      MIT

    • illustrator-mcp

      Christancho-co
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to control Adobe Illustrator on Windows, including creating, opening, saving, and exporting documents, drawing shapes, adding text, and running arbitrary ExtendScript.
      10
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 15 tools

    Disambiguation4/5

    Each tool has a distinct purpose and the descriptions repeatedly cross-reference to prevent misselection (e.g., execute_script vs execute_task, observe vs export). A few name pairs like document/get_document and job_status/connection_status could mislead, but the extensive WHEN TO USE guidance resolves ambiguity.

    Naming Consistency3/5

    All tools share the illustrator_ prefix and most follow verb_noun, but there are notable exceptions: illustrator_document, illustrator_history, illustrator_observe (verb only), and the awkward illustrator_path_import_svg invert the expected verb-first order. The mixed patterns are still readable but not fully consistent.

    Tool Count5/5

    15 tools is an appropriate breadth for an Illustrator control server, covering document lifecycle, shape creation/editing, import/export, observation, validation, and diagnostics. No tool feels redundant, and the count sits comfortably within the ideal range.

    Completeness4/5

    The tool set covers core workflows: document management, structured and raw editing, boolean geometry, SVG import, file placement, export, visual observation, querying, preflight checks, history, and connection/job status. Minor gaps exist (e.g., dedicated text editing or layer management tools depend on execute_task or raw script), but most operations are reachable through structured operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources