Choose a plugin

Start from the outcome, not the model.

I need to…	Use	Why
Roto, key, track, relight, restore, extend, or reconstruct a shot	mere-vfx-tools	Shot-oriented workflows and verified production handoffs
Cut a subject out of a still	mere-image-tools	Focused SAM 3.1 knockout and matte cleanup
Play a local generative music model live	mere-perform	MIDI, stage UI, prompt control, logs, and capture
Build shot, character, voice, or delivery kits	mere-animatic-tools	Animatic-specific artifact bundles
Publish local artifacts for production review	mere-shotgrid-tools	Versions, uploads, Notes, Playlists, and task updates
Train a Klein LoRA on rented GPUs	mere-runpod	Planned user-owned pods, artifact fetch, cleanup by default
OCR and redact a document	mere-doc-tools	Local OCR plus optional local anonymization
Scrub text and PII across frames	mere-media-scrub	Resumable frame-batch privacy workflow
Caption a LoRA dataset	mere-dataset-tools	Captions, OCR sidecars, trigger tokens, contact sheet
Transcribe and redact audio	mere-transcript-tools	Local ASR plus optional anonymization
Repeat an image generation composition	mere-image-compose	Records prompt, references, LoRA, dimensions, seed, and output
Run many explicit core commands	mere-batch-runner	Durable JSONL job status and resumability

Narrow or broad?

Prefer the narrowest plugin that owns the whole workflow. For a single still knockout, Image Tools is simpler than VFX Tools. For a shot that needs roto, tracking, alpha delivery, and QC, VFX Tools owns the larger lifecycle.

Local or provider-backed?

Eleven catalog commands operate locally. RunPod Runner is provider-backed and therefore has stronger planning and cleanup obligations. Read Provider safety before creating paid resources.