Shaka Packager MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TEMP_DIR | No | Custom temporary directory for file uploads | |
| LOG_LEVEL | No | Logging level (DEBUG, INFO, WARNING, ERROR, CRITICAL) | |
| VIDEO_PATH | No | Path to your local video directory (used for translating paths between Docker and host) | |
| DOCKER_PATH | No | Docker container mount path | /projects/video-drop |
| COMMAND_TIMEOUT | No | Timeout in seconds for Shaka Packager commands | 300 |
| SHAKA_PACKAGER_PATH | No | Path to the Shaka Packager executable (highly recommended for Claude Desktop) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_videoB | |
| run_shaka_packagerC | |
| get_shaka_documentationB | Get comprehensive Shaka Packager documentation, including command structure and examples. |
| get_shaka_optionsB | Get the available options and version information for Shaka Packager. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| mp4_to_ts_prompt | Create a prompt to convert MP4 files to TS files. Args: file_path: Path to the uploaded video file. |
| vod_hls_dash_prompt | Create a prompt to package a file for VOD (Video on Demand) in HLS and DASH formats. Args: file_path: Path to the uploaded video file. |
| live_hls_dash_prompt | Create a prompt to package a file for live streaming in HLS and DASH formats. Args: file_path: Path to the uploaded video file. |
| content_encryption_prompt | Create a prompt to encrypt content using Shaka Packager. Args: file_path: Path to the uploaded video file. |
| ad_insertion_prompt | Create a prompt to prepare content for ad insertion using Shaka Packager. Args: file_path: Path to the uploaded video file. |
| analyze_video_prompt | Create a prompt to analyze a video file using Shaka Packager. Args: file_path: Path to the uploaded video file. |
| what_should_i_do_prompt | Create a prompt to suggest operations when the user provides a file path without specific instructions. Args: file_path: Path to the video file. |
| command_format_reminder | Create a prompt to remind about proper Shaka Packager command format. |
| error_interpretation_prompt | Create a prompt to help interpret common Shaka Packager errors. Args: error_message: The error message from Shaka Packager. file_path: Path to the video file that caused the error. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: analyze_video for file analysis, get_shaka_documentation for documentation retrieval, get_shaka_options for version/options info, and run_shaka_packager for custom command execution. There is no overlap or ambiguity between these functions.
All tools follow a consistent verb_noun pattern (analyze_video, get_shaka_documentation, get_shaka_options, run_shaka_packager) with clear, descriptive names. The naming convention is uniform throughout the set.
Four tools is reasonable for a Shaka Packager server, covering core functions like analysis, documentation, options, and execution. However, it feels slightly thin as it lacks tools for common specific operations like packaging or transmuxing, which might be expected in this domain.
The toolset covers basic Shaka Packager interactions but has notable gaps. It provides analysis, documentation, options, and custom execution, but lacks dedicated tools for standard packaging workflows (e.g., create_manifest, package_video) that would complete the surface for media processing tasks.