Google AI Edge Gallery Video MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| edge_video_createB | End-to-end prompt-to-video pipeline powered by Google AI Edge Gallery standards. Plans storyboard scenes, renders keyframes, applies Ken Burns motion and color grading, compiles into MP4, and syncs directly to Android DCIM Gallery / Google Photos. |
| edge_storyboard_planB | Plans a director-level screenplay and storyboard breakdown from a raw prompt, specifying scene shots, camera dynamics, transitions, and timing. |
| edge_generate_keyframesC | Generates visual keyframe cards and assets for each shot in a storyboard. |
| edge_apply_video_fxC | Generates hardware-optimized filtergraphs for Ken Burns camera motion, color balance, and cinematic vignette. |
| edge_compile_videoC | Compiles an existing storyboard, keyframes, transitions, and audio into final MP4 video file. |
| android_device_statusA | Checks Android device battery percentage, thermal throttling status, available storage, and acceleration mode (Termux, ADB bridge, or Host). |
| android_gallery_exportA | Exports any video file to Android DCIM folder and triggers Android MediaStore scanner so it instantly shows up in Google Photos / Gallery. |
| edge_models_managerC | Inspects and manages Google AI Edge Gallery models (Gemma 2, Gemma 3n, MobileDiffusion, MediaPipe tasks). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| ai_video_director | Guides the AI to act as an edge cinematic director, crafting multi-shot video plans for on-device generation. |
| social_shorts_creator | Creates a viral 9:16 vertical short optimized for mobile attention spans, hooks, dynamic captions, and Google AI Edge aesthetics. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Device Telemetry & Acceleration | Real-time battery, thermal, and acceleration stats for Android / Edge runtime. |
| Created Edge Videos Catalog | List of videos stored in Android DCIM or local Edge output folder. |
| Edge AI Models Inventory | Catalog of models compatible with Google AI Edge Gallery. |
TDQS
Scored across 8 tools
edge_video_create is an end-to-end pipeline that subsumes the individual step tools (edge_storyboard_plan, edge_generate_keyframes, edge_apply_video_fx, edge_compile_video), and its gallery-sync step overlaps with android_gallery_export. The modular vs. monolithic paths are explicitly described, so an agent can reason about it, but boundaries remain blurry.
Names are readable snake_case with thematic prefixes (edge_/android_), but the verb/noun ordering is mixed: edge_video_create and edge_storyboard_plan are noun_verb while edge_generate_keyframes, edge_apply_video_fx, and edge_compile_video are verb_noun. The two-domain prefix scheme is a reasonable choice but not fully predictable.
Eight tools is a well-scoped set for a video-generation pipeline, covering planning, keyframes, FX, compile, orchestration, export, device status, and model management without obvious padding.
The surface covers the full prompt-to-MP4 lifecycle plus device/export/model management. Minor gaps exist: edge_compile_video references audio but there is no audio-generation tool, and there is no cleanup/delete for produced assets.