Supported Agents And MCP Clients
Automation Agent for Adobe Premiere is designed to work with the agent or model environment that fits your workflow.
The MCP server is the connection layer. It lets external agents inspect the current Premiere project, validate Runtime DSL, and execute permission-scoped workflows through the Automation Agent panel.
The practical question is not only "which clients support MCP?" It is:
- which agent is strong enough for the workflow?
- which model or provider is allowed for the material?
- does the workflow need live reasoning during execution?
- should the result become a saved script or implementation prompt for reuse?
If you have not made that decision yet, start with Ways To Run Automations.
If you are not sure what Assistant and Workflow AI mean, start with AI Setup Roles. In short: the Assistant is the AI you talk to, while Workflow AI is a provider a saved workflow can call later.
This page is only about MCP clients. If you want to launch a saved script from a shortcut, Stream Deck, or Touch Portal, see Keyboard Shortcuts and Remote Triggers instead.
Automation Agent uses one panel-managed local HTTP helper. The Claude desktop Claude tab uses the bundled local stdio adapter to connect to that helper. Other local clients should connect over HTTP.
Currently Supported and Documented
These are the client paths that are currently supported and documented as first-class workflows:
- Codex in the ChatGPT desktop app
- Claude Code
- Claude tab in Claude Desktop
- LM Studio
Role Overview
| Tool or surface | Assistant | Workflow AI | Notes |
|---|---|---|---|
| ChatGPT desktop app — Codex | yes | macOS often includes the runnable Codex binary; Windows needs separate CLI setup | Verified local MCP surface. Use the Automation Agent skill and MCP config. |
| ChatGPT desktop app — ChatGPT | not supported | no | Skill visibility differs by platform: observed on macOS, absent on Windows. Do not rely on this surface for Automation Agent. |
| ChatGPT web and mobile | no local MCP | no | Hosted sessions do not read the machine's local Codex config or reach its loopback Premiere server. |
| Codex CLI | usually through the same Codex setup | yes | Needs codex login before saved workflows can call it. |
| Claude Desktop Code tab | yes | no | Uses Claude Code with direct local HTTP MCP. |
| Claude Code CLI | optional / advanced | yes | Needs claude auth login; used as the Claude Workflow AI provider. |
| Claude tab in Claude Desktop | yes | no | Uses the MCPB local adapter to the panel-managed helper. |
| LM Studio | advanced / model-dependent | yes | Best used as local Workflow AI, especially for offline or approved-model workflows. |
Recommended Paths By Need
Codex In The ChatGPT Desktop App
Recommended when:
- you want a strong OpenAI-based coding agent for technical Automation Agent workflows
- you have access to Codex, including limited access on some ChatGPT plans
- you want the generated Automation Agent Codex skill and MCP setup to guide discovery, validation, and Runtime DSL authoring
- you may also want Codex CLI as Workflow AI for saved workflows
Transport path:
- panel-managed HTTP MCP server
- open the ChatGPT desktop app and select Codex
Role setup:
- Assistant: configure Codex MCP and install the Automation Agent Codex skill
- Workflow AI: configure and test Codex CLI in AI Setup
Do not use the separate ChatGPT surface for Automation Agent. It does not expose /mcp or call the local Premiere server in either tested installation, and the locally installed skill was visible on macOS but absent on Windows.
See:
Claude Code
Recommended when:
- you want a strong Claude-based coding agent for technical Automation Agent workflows
- you have access to Claude Code
- you want a guided setup with the generated Automation Agent Claude Skill
- you may also want Claude Code CLI as Workflow AI for saved workflows
Transport path:
- panel-managed HTTP MCP server
Role setup:
- Assistant: configure Claude Code MCP and install or confirm the Automation Agent Claude Skill where your Claude surface supports it
- Workflow AI: configure and test Claude Code CLI in AI Setup
See:
Claude tab in Claude Desktop
Recommended when:
- you want a more end-user-facing Claude Desktop chat workflow
- you can accept that, unlike Codex or Claude Code, this client cannot access your project folder directly
- you still want Claude to manipulate files through the Automation Agent MCP workflow
Transport path:
- panel-managed HTTP helper, reached through the Claude Desktop MCPB adapter
Role setup:
- Assistant in the Claude tab: install the MCPB desktop extension and upload the Claude Skill ZIP
- Workflow AI: not supported through Claude tab in Claude Desktop; use Claude Code CLI if you want Claude as Workflow AI
See:
LM Studio
Recommended when:
- you want to run the model locally
- your material or organization requires a local or approved model path
- you want a local MCP-capable chat client
- you can provide more explicit workflow instructions for complex Premiere tasks
- you want a local Workflow AI provider for saved workflows
Transport path:
- panel-managed HTTP MCP server
Role setup:
- Workflow AI: start the LM Studio local server, load a model, and configure LM Studio as a provider in AI Setup
- Assistant: possible for advanced users, but Codex or Claude is usually better for creating complex Automation Agent workflows
See:
Important expectation:
- LM Studio can use Automation Agent as an MCP tool server, but it does not currently receive the same bundled Automation Agent guidance and examples that Codex and Claude workflows can use through their guided setup. For complex workflows, use prepared workflow recipes or detailed implementation prompts.
This is why reusable implementation prompts matter. A local model may be allowed to process sensitive material, but it usually benefits from a more explicit, tested workflow plan.
Other MCP-Capable Clients
Other clients may still work, but they are currently manual / advanced setups, not first-class documented workflows.
Examples include:
- Cursor
- Windsurf
- GitHub Copilot coding agent
- other MCP-capable IDE or agent shells
For HTTP clients, start the panel-managed helper and use the local /mcp URL. The former full stdio server mode has been removed. The Claude Desktop MCPB provides its own local stdio-to-HTTP adapter. We do not currently distribute a standalone adapter for other stdio-only clients; request support for your client if it cannot connect over HTTP.
Important note for manual clients
For Cursor, Windsurf, Copilot, and similar tools, Automation Agent does not currently ship dedicated guided installers in the panel.
Those clients may still be usable, but the MCP setup is currently manual and depends on that client's own MCP support model.
Practical Recommendation
If you want the most reliable current paths:
- Use Codex in the ChatGPT desktop app for the main OpenAI technical workflow.
- Use Claude Code for the main technical Claude workflow.
- Use Claude tab in Claude Desktop for the simpler end-user-facing Claude Desktop workflow.
- Use LM Studio when you need a local model and can work with more explicit prompts.
If you are evaluating another MCP-capable client, first determine whether it needs:
- HTTP -> connect directly to the panel-managed local MCP URL
- stdio -> use the supplied Claude Desktop extension for Claude; standalone adapters for other clients are not currently provided
Then configure that client manually.
For repeated workflows, do not rely on a broad one-line prompt every time. Develop the workflow once with a strong Automation Agent-aware client, then turn the successful run into a reusable implementation prompt or saved script. See Create Your Own Recipes.