Skip to main content

Claude Desktop Setup

The Claude tab in the desktop app can use Automation Agent through a local desktop extension. The extension translates Claude's stdio MCP messages to the same panel-managed HTTP helper used by Claude Code, Codex, and Remote Execution URLs. The extension does not start a second helper or take over its port.

Claude Desktop is an Assistant: you can ask it to inspect Premiere and run Automation Agent tools. To use Claude as Workflow AI inside saved scripts, configure the separate Claude Code CLI provider in Claude Code Setup.

Install or upgrade​

  1. Open Premiere and the Automation Agent panel. In MCP Server, start the local helper and confirm that the panel connects. Leave it running while using Claude.
  2. In AI Setup, open Agent Setup → Claude Desktop → Open Desktop Export Folder.
  3. When replacing an Automation Agent MCP extension in Claude Desktop, remove old or debug copies. Legacy full-server extensions may occupy port 53125. In Claude Desktop, check Settings → Extensions and Developer → Local MCP servers for an older Automation Agent entry. Avoid keeping duplicate entries with the same tools.
  4. In Claude Desktop, open Settings → Extensions → Advanced settings → Install Extension… and select automation-agent-claude-desktop-extension.mcpb from the export folder. The extension uses port 53125 by default. If the panel uses a different port, set Automation Agent MCP port to match in the extension configuration.
  5. Upload automation-agent-claude-skill.zip in Claude Desktop under Customize → Skills.
  6. Fully quit and reopen Claude Desktop, then start a new conversation in the Claude tab.

The MCPB can answer tool discovery even when Premiere is closed. Tool calls then report that the local helper is unavailable. Open Premiere, start the helper, and retry the call. The skill provides guidance but does not establish the MCP connection by itself.

If you previously selected the old Claude Chat mode, helper auto-start stays off after this update. Start it once in the panel, or enable auto-start in MCP Server settings if you want it to start when the panel opens.

Current extensions use a separate adapter compatibility version, so compatible Premiere plugin updates do not require reinstalling the MCPB. Older extensions and helpers without this compatibility metadata still require the same Automation Agent product version. If Claude or the panel reports an incompatible extension, remove the old or debug copy under Settings → Extensions, install the MCPB supplied by your installed Premiere plugin using the steps above, and fully quit and reopen Claude Desktop. Debug MCPBs have separate extension IDs and can remain installed alongside the release extension unless removed. Privately distributed MCPBs require manual updates in Claude.

Verify the connection​

Ask Claude: “Which Automation Agent MCP tools are available? Do not run any tools or change anything in Premiere.” You should see tools such as runDslProgram, startDslRun, and getDslRunStatus. Then use a read-only tool call in a safe project.

If Claude shows Server disconnected, open Settings → Developer → Local MCP servers. An entry whose command points to an old helper/common/server.mjs package is the previous full-server extension. Replace it with the current MCPB. If discovery works but calls fail, check that the panel-managed helper is running and that its port matches the extension setting.

The Code tab uses Claude Code's direct HTTP MCP configuration and does not need the MCPB. See Claude Code Setup. A cloud remote MCP connector cannot reach Premiere's loopback address; use the desktop extension for the local Claude tab.

Rollback​

To roll back, restore the MCPB supplied with the earlier Premiere plugin. Compatible current adapters can span product versions, but legacy adapters and helpers require an exact product-version match. The current plugin no longer supports the old full stdio server; reinstalling only that legacy MCPB is not a supported rollback. Stop the panel-managed helper before switching to an older full-server release, since both processes would otherwise compete for the same port.