clipwright-transcribe
MCP tool to transcribe audio/video files and generate SRT/VTT captions and OTIO timeline.
External Binaries / Files
This tool requires the following external binaries/files to exist in the execution environment. They are not installed via pip, so obtain them separately.
whisper.cpp Binary
Used for transcription.
- Place
whisper-cli(or the binary name appropriate for your environment) on PATH, or specify the full path in theCLIPWRIGHT_WHISPERenvironment variable. - Obtain: Build from https://github.com/ggerganov/whisper.cpp, or use release binaries.
export CLIPWRIGHT_WHISPER=/path/to/whisper-cli
ggml Model File
Speech recognition model (.bin file) used by whisper.cpp.
- Specify the full path to the model file in the
CLIPWRIGHT_WHISPER_MODELenvironment variable. Can be overridden by themodel_pathparameter at tool invocation. - Obtain: Download from https://huggingface.co/ggerganov/whisper.cpp etc.
export CLIPWRIGHT_WHISPER_MODEL=/path/to/ggml-base.bin
ffmpeg
Required to convert audio to 16kHz mono WAV (input format for whisper.cpp).
- Place
ffmpegon PATH, or specify the full path in theCLIPWRIGHT_FFMPEGenvironment variable.
export CLIPWRIGHT_FFMPEG=/path/to/ffmpeg
Environment Variables Summary
| Environment Variable | Purpose | Required |
|---|---|---|
CLIPWRIGHT_WHISPER |
Path to whisper.cpp binary (required if not on PATH) | Conditional |
CLIPWRIGHT_WHISPER_MODEL |
Path to ggml model file (model_path parameter takes precedence) |
Conditional |
CLIPWRIGHT_FFMPEG |
Path to ffmpeg binary (required if not on PATH) | Conditional |
GPU / CUDA Acceleration
clipwright-transcribe supports GPU-accelerated transcription transparently: simply point
CLIPWRIGHT_WHISPER at a CUDA or Metal build of whisper.cpp — no code or parameter changes
are required.
Obtaining a CUDA / Metal Binary
| Platform | How to obtain |
|---|---|
| Windows (CUDA) | Download whisper-cublas-*-bin-x64.zip from whisper.cpp Releases. Extract and set CLIPWRIGHT_WHISPER to the full path of whisper-cli.exe. |
| Linux (CUDA) | Build from source with -DGGML_CUDA=ON: cmake -B build -DGGML_CUDA=ON && cmake --build build -j --config Release. Binary is at build/bin/whisper-cli. |
| macOS (Metal) | brew install whisper-cpp installs a Metal-accelerated build automatically. |
# Windows CUDA example
export CLIPWRIGHT_WHISPER=/path/to/whisper-cublas/whisper-cli.exe
# macOS Metal example (after brew install whisper-cpp)
export CLIPWRIGHT_WHISPER=/opt/homebrew/bin/whisper-cli
Confirming GPU / Backend Usage
The tool envelope includes data.backend and data.realtime_factor so you can verify the
device actually used at runtime:
{
"data": {
"backend": {
"device": "cuda",
"detail": "CUDA"
},
"realtime_factor": 12.5,
"whisper_wall_seconds": 14.2
}
}
data.backend.device— one ofcuda,metal,cpu, orunknown.data.backend.detail— sanitized fixed device label (CWE-209: no raw stderr / model path). Values:"CUDA"(cuda),"Metal"(metal),"cpu"(cpu),""(unknown).data.realtime_factor—audio_duration_sec / whisper_wall_seconds. Values above1.0mean faster than realtime (e.g.12.5means 12.5× faster than realtime); a GPU build typically yields values well above1.0while a slow CPU build may fall below1.0.data.whisper_wall_seconds— raw wall-clock seconds spent in the whisper subprocess.
summary also reports the backend used (e.g. " Backend: cuda (12.5x realtime)."), so
the information is visible in the one-line MCP response without unpacking data.
Note on Python GPU Libraries
clipwright-transcribe does not import faster-whisper, CTranslate2, or any CUDA
Python library. Transcription is always invoked as an external subprocess
(CLIPWRIGHT_WHISPER), keeping GPU acceleration completely separate from the package
install and preserving license independence. Any whisper-cli-compatible binary — CPU,
CUDA, Metal, ROCm — can be used by updating the environment variable alone.
MCP Tool
clipwright_transcribe(media, output, options?) — Transcribe audio/video file and generate output.otio / output.srt / output.vtt.
Metadata
Release files for clipwright-transcribe 0.6.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| clipwright_transcribe-0.6.1.tar.gz | 18.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| clipwright_transcribe-0.6.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.9 kB
Release files / clipwright_transcribe-0.6.1.tar.gz
| Download URL | clipwright_transcribe-0.6.1.tar.gz |
|---|---|
| Size | 18.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f836e21018fe02b60beeb9d948158996c53485c7166200f0611ee208fd0d9b23
|
|
BLAKE2b-256 checksum How to use checksums |
d6ca4d1b2902df47a85f9c05f447f9f2ae4419564ee84846f2e26272a4220a7b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 20, 2026.
Transparency logRelease files / clipwright_transcribe-0.6.1-py3-none-any.whl
| Download URL | clipwright_transcribe-0.6.1-py3-none-any.whl |
|---|---|
| Size | 21.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2c4fb6918d158fea7a551a0a596a00e3cb87de8ddf644358b83ac242be979218
|
|
BLAKE2b-256 checksum How to use checksums |
50ad302187586b776d800ff30a30c8c5e33b5835a64cf1bdeb1baa33a33a94eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 20, 2026.
Transparency log