media-context-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WHISPER_BIN | No | Path to the whisper binary, if not on PATH | |
| TESSERACT_BIN | No | Path to the tesseract binary, if not on PATH |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_media_depsA | Report which external binaries (ffmpeg, ffprobe, yt-dlp, whisper, tesseract) are available. Call this first if analyze_media fails with a missing-binary error. |
| analyze_mediaA | Turn a local media file or URL (video, audio, or image) into compact context a model can read — fully local, no paid APIs. Video: montage frames (mode 'sheet', cheapest default), individual stills ('frames'), or scene changes ('scenes'); add transcript and/or ocr. Audio: speech transcript. Image: the picture plus optional OCR. For app/screen recordings use detail:'high' + ocr:true. To catch a transient UI glitch (a flicker/jump lasting <1s), use mode:'filmstrip' with a narrow startSec/endSec window, a high fps (10–15), and a crop around the affected control — it stacks dense frames so you can spot a frame whose value disagrees with the visual. Use the cheap default for everything else. Pass context to frame the analysis. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: analyze_media handles media content analysis, while check_media_deps checks for required external binaries. There is no overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern using snake_case (analyze_media, check_media_deps), making them predictable and easy to understand.
With only two tools, the set is minimal but appropriate for a focused utility server. The main tool is comprehensive, and the second tool provides essential support. A slightly larger set might allow more granular operations, but the current count is not problematic.
The analyze_media tool covers video, audio, and image analysis comprehensively with multiple modes and options. The check_media_deps tool fills the essential dependency-checking role. No obvious gaps are present for the server's stated purpose.