Adobe Studio MCP
Related Servers
Alternatives to Adobe Studio MCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceEnables AI assistants to control Adobe After Effects via MCP, including creating compositions, managing layers, setting keyframes and expressions, applying effects, and swapping footage/comps in batch operations.13182 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseAqualityBmaintenanceEnables local control of Adobe After Effects via MCP, offering offline creative skills, project inspection, and operation execution without cloud relay or an installed AE panel.122,219 npm13MIT
- AlicenseCqualityCmaintenanceEnables controlling Adobe After Effects from an MCP client through a bridge panel running inside AE. Supports composition and layer automation, effect and preset application, keyframing, markers, and audio waveform analysis for generating markers.30182 npmMIT
- AlicenseAqualityBmaintenanceEnables 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.53,657 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants and autonomous agents to control professional creative applications such as Photoshop, Blender, and CapCut through a unified local-first MCP gateway with native automation and secure multi-client multiplexing.Apache 2.0
TDQS
Scored across 182 tools
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.
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.
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.
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.