Protocol-driven LLM integration into professional creative tools
Adobe MCP Servers
Two Model Context Protocol servers that let an LLM operate After Effects and Premiere Pro directly, validating every tool call.
- Role
- Sole engineer, designer, and operator
- Year
- 2025
- Status
- In Development
- TypeScript
- Model Context Protocol (MCP) SDK
- Zod (schema-validated tool definitions)
- CEP / ExtendScript (Adobe integration runtime)
- Adobe After Effects / Premiere Pro
43 of 97 defined
Tools validated against a live Premiere Pro session
2025 · T-Mobile AI engineering stretch assignment; walkthrough on request
Challenge
An LLM can’t natively drive a professional NLE or motion graphics app. After Effects and Premiere Pro script through ExtendScript, an old ES3-only dialect inside Adobe’s CEP panel runtime, which a modern model can’t call directly or safely. Every tool call had to be validated before touching a project file.
Process
Each server is TypeScript on the official MCP SDK. Every tool has a Zod schema, so calls are validated before reaching Adobe. With no direct process bridge into CEP, commands go by file-based IPC to an ExtendScript runtime in the panel, under an ES3-compatibility ruleset: no modern JavaScript in that layer, careful serialization across the file boundary, and defensive tool definitions.
Both servers live in private repositories with no public code link; I demo them live or by recorded walkthrough on request. They define 97 tools; 43 are validated end to end against a live Premiere Pro session, with the rest in progress.
Result
An LLM now works inside a professional creative pipeline (After Effects and Premiere Pro), built and proven within enterprise IT constraints. It is internal tooling for a video production team, not a commercial product, and the 43 validated tools already support real work.