Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Scout for Premiere Pro

MCPB · SCOUT-PREMIERE-MCP-0.3.0.MCPB · SCANNED SEP 21

Drive Adobe Premiere Pro from an AI agent: transcript search, markers, cuts, exports, 277 tools.

+3 this week 47 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security13
  • Malware scan not yet available for this package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
  • No install/post-install scripts declared.Pass
  • Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • License check failed: the license (SEE LICENSE IN https://www.trevorohare.com/policies) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 20 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 14753 tokens (~53/item across 277 items; 277 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 19 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_markers" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 277 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

mcpb · scout-premiere-mcp-0.3.0.mcpb

Download bundle
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 +3
    • Stability: unverified → 0.23 functional
  • 1 Sept 26 38

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Analysed mcpb/https://github.com/tro2789/scout-premiere-mcp/releases/download/v0.3.0/scout-premiere-mcp-0.3.0.mcpb@0.3.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb

Background: How many MCP packages publish verified provenance →

MCP tools · 277 exposed · ~14,753 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
list_available_effects ~19

Lists all available video effects in Premiere Pro.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_available_transitions ~19

Lists all available video transitions in Premiere Pro.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_clip_effects ~19

Premiere Pro expanded operation: list clip effects.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_markers ~110

List markers on the active sequence with start seconds, duration seconds, name, comment, type, and color index. Optionally filter by name prefix (e.g. 'Scout/Social:' to see only Social Clips markers added by Scout). The result always includes activeSequence {name, id} — the sequence this call actually ran against. Compare it across calls to detect the user switching sequences in Premiere mid-session.

NameTypeReqDescription
prefixstringOptional. Only return markers whose name starts with this string.

No output schema declared.

No examples provided.

list_project_items ~67

Lists all media items, bins, and assets in the current Premiere Pro project. Use this to discover available media before performing operations.

NameTypeReqDescription
includeBinsbooleanWhether to include bin information in the results
includeMetadatabooleanWhether to include detailed metadata for each item

No output schema declared.

No examples provided.

list_sequence_tracks ~59

Lists all video and audio tracks in a specific sequence with their properties and clips.

NameTypeReqDescription
sequenceIdstringyesThe sequence ID (GUID) to list tracks for, as returned in the "id" field by list_sequences or get_active_sequence

No output schema declared.

No examples provided.

list_sequences ~27

Lists all sequences in the current Premiere Pro project with their IDs, names, and basic properties.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lock_track ~101

Locks or unlocks a track to prevent/allow editing. The sequence does not have to be the active one.

NameTypeReqDescription
lockedbooleanyesWhether to lock (true) or unlock (false)
sequenceIdstringyesThe sequence ID (GUID) as returned in the "id" field by list_sequences or get_active_sequence
trackIndexnumberyesThe index of the track
trackTypestringyesType of track

No output schema declared.

No examples provided.

match_frame ~16

Premiere Pro expanded operation: match frame.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

move_clip ~106

Moves a clip along the timeline, keeping it on its current track. To move a clip to a different track, use move_clip_to_track: on this Premiere build that is a remove-and-reinsert, which can overwrite whatever occupies the destination and gives the clip a new id, so it is deliberately a separate call rather than an option here.

NameTypeReqDescription
clipIdstringyesThe ID of the clip to move
newTimenumberyesThe new time position in seconds

No output schema declared.

No examples provided.

move_clip_to_track ~20

Premiere Pro expanded operation: move clip to track.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

move_item_to_bin ~53

Moves a project item into a different bin (folder).

NameTypeReqDescription
projectItemIdstringyesThe ID of the project item to move
targetBinIdstringyesThe ID of the destination bin

No output schema declared.

No examples provided.

move_items_to_bin ~20

Premiere Pro expanded operation: move items to bin.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

move_playhead_to_edit ~22

Premiere Pro expanded operation: move playhead to edit.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

multiple_undo ~17

Premiere Pro expanded operation: multiple undo.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mute_track ~66

Mutes or unmutes an entire audio track.

NameTypeReqDescription
mutedbooleanyesWhether to mute (true) or unmute (false) the track
sequenceIdstringyesThe ID of the sequence
trackIndexnumberyesThe index of the audio track

No output schema declared.

No examples provided.

nest_clips ~17

Premiere Pro expanded operation: nest clips.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

open_in_source ~18

Premiere Pro expanded operation: open in source.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

open_project ~39

Opens an existing Adobe Premiere Pro project from a specified file path.

NameTypeReqDescription
pathstringyesThe absolute path to the .prproj file to open

No output schema declared.

No examples provided.

overwrite_clip ~16

Premiere Pro expanded operation: overwrite clip.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

overwrite_from_source ~18

Premiere Pro expanded operation: overwrite from source.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ping ~14

Premiere Pro expanded operation: ping.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

place_markers ~198

Add markers to the active sequence. Each marker has startSec (required) and optional endSec (omit for a point marker, include for a duration marker). All markers in one call share a single colorName. Use the Scout namespace convention for `name` (e.g. 'Scout/Social: Hook intro', 'Scout/Cleanup: Dead air', 'Scout/Key: Topic shift') so other tools and the panel UI can find them by prefix later. Markers are added non-destructively — existing markers are not touched. The result always includes activeSequence {name, id} — the sequence this call actually ran against. Compare it across calls to detect the user switching sequences in Premiere mid-session.

NameTypeReqDescription
colorNamestringColor applied to all markers in this batch. Defaults to GREEN. Note Adobe's enum spells magenta 'MAGNETA' — typo in the constants.
markersarrayyes

No output schema declared.

No examples provided.

play_source_monitor ~18

Premiere Pro expanded operation: play source monitor.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

play_timeline ~17

Premiere Pro expanded operation: play timeline.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

razor_all_tracks ~18

Premiere Pro expanded operation: razor all tracks.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

razor_at ~386

Cut tracks in the active sequence at each provided sequence-time (in seconds). Produces no content removal — just adds cut boundaries, the same effect as Premiere's Razor tool (Ctrl+K) applied at each point. Reversible with Ctrl+Z in Premiere. Requires the CEP helper to be running. Optional `scope` selects which tracks are cut: 'all' (default — every video AND audio track), 'video' (every video track only), 'audio' (every audio track only), or 'track' (one specific track — `trackType` and `trackIndex` are then REQUIRED; they are invalid with any other scope; enforced in the handler since the schema cannot express the pairing). CAVEAT: per-track cuts (scope video/audio/track) unlink audio from video on the cut clips — Premiere's QE per-track razor behaves that way; scope 'all' cuts through everything at once. Use this when Claude needs to introduce cuts without the full Lift/Extract flow — e.g., 'cut the timeline at the 10 speaker transitions' followed by a manual review. The result always includes activeSequence {name, id} — the sequence this call actually ran against. Compare it across calls to detect the user switching sequences in Premiere mid-session.

NameTypeReqDescription
scopestringWhich tracks to cut. Default 'all'. 'video'/'audio' cut every track of that type; 'track' cuts exactly one track (requires trackType + trackIndex).
secondsarrayyesSequence-time positions (in seconds) at which to cut.
trackIndexintegerRequired when scope='track', invalid otherwise. 0-based track index (V1 = video 0, A1 = audio 0).
trackTypestringRequired when scope='track', invalid otherwise. Type of the single track to cut.

No output schema declared.

No examples provided.

razor_timeline_at_time ~115

Cuts across multiple tracks in a sequence at an absolute timeline time. If no track arrays are provided, all video and audio tracks are cut.

NameTypeReqDescription
audioTrackIndicesarrayOptional audio track indices to cut. Defaults to all audio tracks.
sequenceIdstringOptional sequence ID. Defaults to the active sequence.
timenumberyesAbsolute timeline time in seconds where the cut should occur.
videoTrackIndicesarrayOptional video track indices to cut. Defaults to all video tracks.

No output schema declared.

No examples provided.

read_sequence_captions ~131

Reads caption tracks of a sequence, returning each caption clip as { start, end, text } in seconds. IMPORTANT: Premiere Pro exposes no caption-read API in its scripting DOM, so in practice this returns trackCount:0 / captions:[] even when the sequence HAS a working caption track. The response field captionReadSupported:false (plus note) signals this — a 0 result does NOT mean the sequence has no captions. To read cue text/timing, parse the source .srt file directly instead.

NameTypeReqDescription
sequenceIdstringOptional sequence ID. Defaults to the active sequence.

No output schema declared.

No examples provided.

redo ~14

Premiere Pro expanded operation: redo.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

refresh_media ~40

Refreshes the media for a project item, reloading it from disk.

NameTypeReqDescription
projectItemIdstringyesThe ID of the project item to refresh

No output schema declared.

No examples provided.

relink_media ~59

Relinks an offline or moved media file to a new file path.

NameTypeReqDescription
newFilePathstringyesThe new absolute file path to relink to
projectItemIdstringyesThe ID of the project item to relink

No output schema declared.

No examples provided.

remove_all_effects ~19

Premiere Pro expanded operation: remove all effects.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

remove_effect ~16

Premiere Pro expanded operation: remove effect.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

remove_effect_by_name ~20

Premiere Pro expanded operation: remove effect by name.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

remove_from_timeline ~100

Removes a clip from the timeline. Pass sequenceId when the clip ID came from list_sequence_tracks for a non-active sequence.

NameTypeReqDescription
clipIdstringyesThe ID of the clip on the timeline to remove
deleteModestringWhether to ripple delete (close gap) or lift (leave gap)
sequenceIdstringOptional sequence ID to search. If omitted, searches the active sequence first, then all sequences.

No output schema declared.

No examples provided.

remove_keyframe ~81

Removes a keyframe from a clip component parameter at a specific time.

NameTypeReqDescription
clipIdstringyesThe ID of the clip
componentNamestringyesThe display name of the component
paramNamestringyesThe display name of the parameter
timenumberyesThe time in seconds of the keyframe to remove

No output schema declared.

No examples provided.

remove_keyframe_range ~20

Premiere Pro expanded operation: remove keyframe range.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

remove_markers ~200

Remove markers from the active sequence. Provide AT LEAST ONE filter: `prefix` (removes every marker whose name starts with the prefix — common case for cleaning up a batch you placed earlier) and/or `startSecMatches` (an array of start times in seconds; matches within ±0.05s tolerance — useful for surgical removal of specific markers identified via list_markers). At least one filter is required; the call fails if both are omitted (no wildcard remove-all). When both are given, a marker only needs to match ONE of them to be removed. The result always includes activeSequence {name, id} — the sequence this call actually ran against. Compare it across calls to detect the user switching sequences in Premiere mid-session.

NameTypeReqDescription
prefixstringRemove all markers whose name starts with this prefix.
startSecMatchesarrayRemove markers whose start time matches one of these (±0.05s).

No output schema declared.

No examples provided.

remove_selected_clips ~19

Premiere Pro expanded operation: remove selected clips.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

rename_bin ~16

Premiere Pro expanded operation: rename bin.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

rename_clip ~16

Premiere Pro expanded operation: rename clip.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

rename_project_item ~74

Renames a project item (sequence, bin, clip) by setting its name. Use this when duplicate_sequence does not propagate the new name to the project panel.

NameTypeReqDescription
newNamestringyesThe new name for the project item
projectItemIdstringyesThe ID of the project item to rename

No output schema declared.

No examples provided.

rename_track ~16

Premiere Pro expanded operation: rename track.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

replace_clip ~72

Replaces a clip on the timeline with another media item.

NameTypeReqDescription
clipIdstringyesThe ID of the clip to replace
newProjectItemIdstringyesThe ID of the new project item to use
preserveEffectsbooleanWhether to keep effects and settings (default: true)

No output schema declared.

No examples provided.

replace_clip_media ~18

Premiere Pro expanded operation: replace clip media.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

reverse_clip ~50

Reverses the playback of a clip.

NameTypeReqDescription
clipIdstringyesThe ID of the clip to reverse
maintainAudioPitchbooleanWhether to maintain audio pitch (default: true)

No output schema declared.

No examples provided.

ripple_delete ~16

Premiere Pro expanded operation: ripple delete.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

roll_edit ~16

Premiere Pro expanded operation: roll edit.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

save_project ~17

Saves the currently active Adobe Premiere Pro project.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the Scout for Premiere Pro MCP server?

Scout for Premiere Pro is an MCP server listed in the public MCP registry as io.github.tro2789/scout-premiere-mcp. Drive Adobe Premiere Pro from an AI agent: transcript search, markers, cuts, exports, 277 tools. This page covers its MCPB bundle (https://github.com/tro2789/scout-premiere-mcp/releases/download/v0.3.0/scout-premiere-mcp-0.3.0.mcpb).

Is the Scout for Premiere Pro MCP server safe to use?

Scout for Premiere Pro scores 47 out of 100 on VerifyMCP. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Scout for Premiere Pro MCP server expose?

Scout for Premiere Pro exposes 277 tools: get_active_sequence, get_transcript, find_words, list_markers, place_markers, and 272 more. Their descriptions and schemas cost roughly 14,753 tokens of context every time the server is loaded.