
Scout for Premiere Pro
io.github.tro2789Published by GitHub account tro2789v0.3.0Updated Oct 24, 2026
Drive Adobe Premiere Pro from an AI agent: transcript search, markers, cuts, exports, 277 tools.
Overview
A local bridge that lets an AI assistant drive Adobe Premiere Pro on Windows: search transcripts, place markers, cut, and export via 277 tools.
- What you can do
- Read the active sequence: name, frame rate, duration, timecode and per-track summary, plus the full stitched transcript with sequence-time segments and word-accurate search returning exact times and timecodes. Manage markers: list, place, remove, convert duration markers into chapter markers, and export a CSV of markers by prefix. Edit the timeline: razor cuts at exact sequence times, lift or extract cleanup ranges after backing up the sequence, and re-enable all clips in one undo step. Use the larger ExtendScript tool set for effects, transitions, exports, project and bin management, track targeting and metadata.
- When to use it
- Worth adding if you edit in Premiere Pro on Windows and want an assistant to work on the open timeline — finding spoken words in a transcript, marking or cutting at exact times, or running export and project operations — instead of doing it by hand.
- Requirements
- Windows 10 or 11, Adobe Premiere Pro 26.2 or newer with the licensed Scout extension installed, and the MCP server enabled in the Scout panel. The panel and bridge must run on the same machine; the bridge is a local stdio process (Node 18 or newer if run directly) and uses a localhost WebSocket, port 18803 by default via SCOUT_MCP_PORT. Transcripts require running Premiere's own Transcribe on the sequence first.
Installation
In SourceWeft
- Open Scout for Premiere Pro in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Scout for Premiere Pro: MCP server
Scout is a commercial extension for Adobe Premiere Pro (Windows, Premiere 26.2 or newer). It cuts multi-camera podcasts from the audio and connects AI agents to your timeline over the Model Context Protocol.
This repository hosts the MCP bridge as a downloadable bundle and is the public issue tracker for Scout. The extension's source code is not public.
- Get Scout ($59, one time): https://trevorohare.gumroad.com/l/scout4premiere
- Product page and demo video: https://www.trevorohare.com/dev
- Bug reports and feature requests: open an issue here, using one of the templates
- Community and support: https://discord.gg/qYkacEyfUQ
What the server exposes
The bridge talks to the Scout panel running inside Premiere. It exposes two tool families on one MCP surface:
Panel tools (11). These read Premiere's own transcript and act on the active sequence.
ExtendScript tools (266). Effects, transitions, exports, project and bin management, track targeting, metadata, and more. Adapted from the MIT-licensed adobe-premiere-pro-mcp tool layer; see THIRD-PARTY-LICENSES.md. The full reference is in TOOLS.md.
Install
Scout's Windows installer registers the bridge with Claude Code automatically when the claude CLI is present. For other clients:
Claude Desktop. Download scout-premiere-mcp-<version>.mcpb from Releases and open it. Claude Desktop installs it as an extension.
Claude Code, Cursor, and other stdio clients. Point the client at the installed executable:
Then open the Scout panel in Premiere and turn on Enable MCP Server. The panel shows a live connection indicator and a log of every tool call.
Running the bundle directly
server/index.cjs is the same single-file build that ships inside the .mcpb (sha256 52fbc2dbe35ebbee1135db726d3c2fb78819027c574e84078cebab8603362a41). Any MCP client can launch it with Node 18 or newer:
The Dockerfile builds an image that runs it over stdio. Without Premiere and the Scout panel on the same machine the server still starts and lists its tools; calls that need the panel return a "panel not connected" error.
Requirements
- Windows 10 or 11
- Adobe Premiere Pro 26.2 or newer with the Scout extension installed and licensed
- Scout's MCP server enabled in the panel
- Transcripts: run Premiere's own Transcribe on the sequence first.
get_transcriptandfind_wordsread that transcript; no external transcription service is involved.
Privacy Policy
The bridge runs entirely on your machine. It relays tool calls between your MCP client and the Scout panel over a localhost WebSocket (port 18803 by default) and makes no network requests of its own. Transcript text and sequence data go only to the MCP client you connected. Scout's in-panel AI Analysis feature is separate and uses whichever AI provider you configure in the panel. Full policy: https://www.trevorohare.com/privacy-policy
License
The bundle is proprietary software, licensed to Scout customers under the terms at https://www.trevorohare.com/policies. Third-party components are listed in THIRD-PARTY-LICENSES.md.
Source: README.md at commit 4e68df9
Tools
0Version history
1- v0.3.0LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.