Setup and recovery

Premiere Pro MCP not connecting?

Find the failing step before trying another edit. Start with a disposable project and the read-only check.

Safely check my Premiere connection with verify_premiere_connection. Make no changes.

My assistant cannot see Premiere tools

Confirm that the MCP server was installed in the same client you are using. The Claude Desktop bundle and the Premiere connector are separate installations.
Restart the client after configuration changes. For npm setup, confirm Node.js meets the documented minimum and the configured executable resolves.
For protocol discovery failures, follow the documented legacy-mode recovery in the README. Do not paste arbitrary configuration from an unrelated client.

Check that you installed the Premiere connector as well as the AI-client server. Installing the Claude bundle alone does not add a Premiere panel.
Fully quit and restart Premiere. For the default CEP route, look under Window > Extensions for MCP for Adobe Premiere Pro.
Review the matching release instructions for your OS and connector. UXP and CEP installation steps differ; do not switch bridges simply because one tool is unavailable.

Keep Premiere, the client, and the server on the same computer for the recommended route. Open a disposable project and select a sequence.
Run the read-only connection check again and use its reported missing state. A running panel or successful local doctor check does not establish a live connection.
Do not point the client at the public hosted endpoint as a shortcut. It requires authentication and does not automatically connect to your desktop.

Stop the recipe. Inspect the actual tools available in this session and compare your package and connector versions with the release notes.
The source catalog can include unreleased work. UXP operations also require a compatible connected host and advertised capabilities.
Report the bounded error code, OS, client, and version if you need help. Do not bypass the capability check or substitute an arbitrary script.

Inspect the disposable project before retrying. A partial or unverified result may require human recovery; it is not a successful completion.
Recapture current targets before any later preview. Keep the operation's normal confirmation and revision checks.
For frame exports, inspect the actual files. For an edit, check the timeline, playback, and rendered output separately. Use Premiere's normal Undo or restore your test copy when appropriate.

Once the connection reports ready, start with the sequence check. Do not treat readiness as proof that an edit completed.