Drive Adobe CC (AE, Photoshop, Illustrator, Premiere, Character Animator) from any MCP client
Drive Adobe CC (AE, Photoshop, Illustrator, Premiere, Character Animator) from any MCP client
Drives After Effects, Photoshop, Illustrator, Premiere Pro (and Character Animator puppet authoring) from Claude. See ROADMAP.md for the full tool matrix and what is next. Bridge: MCP client → this server → AppleScript DoScript → AE → temp result file → back.
The server ships on npm as @ajsmonty/adobe-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Once Adobe is connected, these are the calls the assistant has available:
run_extendscript — Run arbitrary JSX; return comes back as JSON. Auto undo-groupedget_project_state — Project item tree, or one comp's layers in detail (comp_name)save_frame — Render a comp frame to PNG, returned inline so Claude can see its worklist_ae_scripts — List .jsx/.jsxbin tools in scripts/ with descriptions from header commentsrun_ae_script — Execute a library script, like File → Scripts → Run Script FileCursor — Settings → MCP → Add server, or edit ~/.cursor/mcp.json (global) / .cursor/mcp.json (per-project):Windsurf — ~/.codeium/windsurf/mcp_config.json — same mcpServers shape as Claude Desktop/Cursor aboveYou will need one environment variable: AE_APP_NAME. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
run_extendscript — Run arbitrary JSX; return comes back as JSON. Auto undo-grouped.get_project_state — Project item tree, or one comp's layers in detail (comp_name).save_frame — Render a comp frame to PNG, returned inline so Claude can see its work.list_ae_scripts — List .jsx/.jsxbin tools in scripts/ with descriptions from header comments.run_ae_script — Execute a library script, like File → Scripts → Run Script File.Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| run_extendscript | Run arbitrary JSX; return <value> comes back as JSON. Auto undo-grouped. |
| get_project_state | Project item tree, or one comp's layers in detail (comp_name). |
| save_frame | Render a comp frame to PNG, returned inline so Claude can *see* its work. |
| list_ae_scripts | List .jsx/.jsxbin tools in scripts/ with descriptions from header comments. |
| run_ae_script | Execute a library script, like File → Scripts → Run Script File. |
{
"mcpServers": {
"adobe": {
"command": "npx",
"args": ["-y", "@ajsmonty/adobe-mcp"],
"env": {
"AE_APP_NAME": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| AE_APP_NAME | Configuration value read at startup. | Optional |
Feed real design data to your coding assistant — layout, tokens and components straight from Figma files.
Integrates Figma's API with Claude and other Model Context Protocol (MCP) compatible clients, providing read-only access to Figma files and projects.
Manages courses, assignments, enrollments, and grades within Canvas using the Canvas API.
Provides a unified TypeScript interface for LLMs to interact with various 3D software applications.
Generates Vue 3 components from Figma designs, adhering to Hostinger's design system.
Enables Cursor AI to interact with Figma, allowing programmatic design modification and data extraction.