Skip to main content
Glama

Related Servers

Alternatives to Adobe Studio MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients like Claude Code, Claude Desktop, and VS Code to build and edit inside a running Adobe After Effects, covering comps, layers, keyframes, effects, text animators, markers, and renders. It supports batched tool calls with single-step undo, frame previews for self-verification, reusable style tokens, and four one-call studio rigs.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to operate local Adobe Premiere Pro projects, covering media ingest, bins, sequence and timeline editing, transitions, effects, keyframes, captions, markers, metadata, proxies, multicam, color, audio, and exports through 283 discoverable tools, 13 context resources, and 10 guided prompts. A bundled CEP panel provides the supported production bridge, with read-only connection verification and higher-level workflows for assembling product spots and motion-graphics demos.
      5
      3,657 npm
      MIT

    TDQS

    B3.2/5.0

    Scored across 182 tools

    Disambiguation3/5

    The app prefixes (ps_, ai_, ae_, pr_, xapp_) make broad selection manageable, and most tools have distinct actions. However, there are many overlapping escape-hatch tools such as adobe_runScript, xapp_bridgeTalk, ps_actionManager, ps_runMenuCommand, ae_executeCommand, and catalog tools, plus generic property setters versus specific transform/keyframe setters. These overlaps will cause misselection despite detailed descriptions.

    Naming Consistency4/5

    Tool names consistently use an app or domain prefix followed by a camelCase action or noun, which makes them predictable across Photoshop, Illustrator, After Effects, Premiere, cross-app, media, and Adobe-level groups. Minor deviations exist in noun-only and multi-operation names like ps_layerOps, ai_layers, pr_tracks, adobe_status, and adobe_batch, so the pattern is not perfectly uniform.

    Tool Count1/5

    At 182 tools, the surface is far beyond a well-scoped set and creates a severe selection burden for an agent. Although the server spans four Adobe apps plus media and plugin management, the sheer volume is an extreme mismatch for practical tool coherence.

    Completeness5/5

    The tool surface is extremely comprehensive across Photoshop, Illustrator, After Effects, and Premiere, covering documents, layers, effects, keyframes, rendering, captions, cross-app workflows, media handling, and plugin management. Generic scripting and catalog tools provide escape hatches for gaps, so there are no obvious dead ends for the stated Adobe automation domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues