Skip to main content

Supported MCP Clients

Automation Agent for Adobe Premiere exposes an MCP server so external agents can inspect and manipulate the current Adobe Premiere project through the Automation Agent panel.

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.

The important distinction is not just whether a client supports MCP in principle, but which transport path that client expects:

  • some clients work best with the panel-managed HTTP MCP server
  • some clients work best with a client-launched local stdio runtime

Currently Supported and Documented​

These are the client paths that are currently supported and documented as first-class workflows:

  1. OpenAI Codex
  2. Claude Code
  3. Claude Desktop Chat
  4. LM Studio

OpenAI Codex​

Recommended when:

  • you want a ChatGPT-based agent
  • you have access to Codex, including limited access on some ChatGPT plans

Transport path:

  • panel-managed HTTP MCP server

See:

Claude Code​

Recommended when:

  • you want a Claude-based agent
  • you have access to Claude Code

Transport path:

  • panel-managed HTTP MCP server

See:

Claude Desktop Chat​

Recommended when:

  • you want to use the Claude Desktop Chat tab
  • 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:

  • Claude Desktop-launched local stdio runtime

See:

LM Studio​

Recommended when:

  • you want to run the model locally
  • you want a local MCP-capable chat client
  • you can provide more explicit workflow instructions for complex Premiere tasks

Transport path:

  • panel-managed HTTP MCP server

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.

Currently Not Supported as a First-Class Workflow​

Claude Desktop Cowork​

The Cowork tab is currently not a supported local Automation Agent workflow.

At the moment, the documented Claude Desktop local path is:

  • Chat tab + MCPB desktop extension + Claude skill ZIP

The documented technical Claude path is:

  • Code tab / Claude Code + HTTP MCP config

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 those clients, the key question is:

  • does the client expect an HTTP MCP server?
  • or does it expect a local stdio process?

If the client expects HTTP​

Use the panel in:

  • Local HTTP MCP transport

That means:

  • start the panel-managed MCP server
  • use the local HTTP MCP URL
  • configure the client manually with the matching MCP entry

If the client expects stdio​

Use the panel in:

  • stdio MCP transport

That means:

  • do not use the panel-managed HTTP server path
  • let the client launch the local stdio runtime itself
  • configure that client manually according to its own local MCP process model

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:

  1. OpenAI Codex for the main OpenAI technical workflow
  2. Claude Code for the main technical Claude workflow
  3. Claude Desktop Chat for the simpler end-user-facing Claude Desktop workflow
  4. 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 -> use Local HTTP MCP
  • stdio -> use stdio MCP

Then configure that client manually.