Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MOTIONFORGE_ROOTSYesMandatory. Absolute paths of authorized project roots. Multiple roots use `:` on macOS/Linux, `;` on Windows. Authorize both application source and output directory.
MOTIONFORGE_BROWSER_PATHNoOptional. Absolute path to the installed Chromium/Chrome executable that Remotion can use; otherwise its renderer may need its own browser download.

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
analyze_projectC

Inspect bounded source inventory, framework, scripts, route evidence, assets and branding.

discover_routesB

Find filesystem route candidates with source paths and explicit inference confidence.

detect_brand_identityB

Extract existing source colors, font declarations and real headings without inventing branding.

analyze_user_flowsB

Return actual route evidence for a client to author flows. Static scanning cannot verify runtime journeys.

inspect_media_assetsB

Inventory local image, font, video and audio assets and byte sizes.

prepare_capture_environmentB

Check project commands and capture URL; does not execute arbitrary project scripts or start a server.

capture_pageB

Capture authentic screenshot in isolated browser; fields/private elements masked and third-party requests blocked.

capture_user_flowC

Execute explicitly authorized bounded actions and capture the final real page state.

record_browser_interactionC

Record real browser interactions through continuously masked screenshots, cursor choreography and measured frame timing; exports local MP4.

capture_responsive_screensC

Capture an explicitly chosen responsive viewport matrix.

inspect_animation_opportunitiesB

Inspect actual headings, links, overflow and Web Animations timing for motion planning; writes evidence screenshot.

generate_creative_briefC

Build an evidence-grounded creative brief from source identity, actual routes and explicit audience/goal.

generate_storyboardC

Validate evidence-bound shots and persist a real renderable timeline. Client supplies product claims and screenshots.

create_scene_planB

Calculate exact scene frame ranges from a validated timeline.

analyze_visual_rhythmB

Measure shot lengths, repetition and readability timing without inventing aesthetic scores.

plan_transitionsB

Return implemented transition types with their timeline positions; no random transition assignment.

generate_remotion_projectC

Export actual editable React/Remotion source, validated timeline and local assets.

create_motion_sceneB

Validate and append a real shot to a new timeline file; no destructive overwrite.

animate_product_interfaceC

Set implemented push, pan, reveal or hold choreography on a real timeline shot.

create_typography_animationC

Create frame-driven typography reveal on a selected shot.

create_camera_movementC

Apply deterministic camera motion to an existing scene.

create_transitionC

Apply a supported fade, wipe or cut transition in a new timeline.

generate_device_mockupC

Frame an actual screenshot with an animated device border; no stock device download.

generate_3d_sceneC

Apply deterministic CSS perspective rotation to a product screen. No mesh/Three.js scene generation.

generate_voiceover_scriptB

Create a timed script from client-authored evidence-bound scene copy; preserves provided language.

generate_voiceoverC

Optionally synthesize supplied text with ElevenLabs. Explicit upload permission and paid account credentials required.

import_audioC

Copy a local authorized music/voice track with license provenance.

plan_sound_designB

Calculate scene boundaries and audio cue windows from actual timeline without downloading music.

sync_audio_timelineC

Attach an authorized local audio file to an exported timeline.

mix_audioC

Mix real local tracks with bounded gain/delay and output limiter via FFmpeg.

configure_renderB

Validate and save dimensions, frame rate, duration and encoding configuration as a renderable timeline.

render_videoC

Render a bounded real H.264 MP4 with Remotion and retain editable project and progress log.

inspect_renderC

Read actual FFprobe streams and container metadata.

export_projectC

Export a standalone editable Remotion project with source assets and npm manifest.

export_videoC

Validate the complete video stream before copying a local MP4 artifact.

validate_timelineA

Validate schema, timings, local assets and bounds before rendering.

analyze_rendered_framesB

Decode the video; run black/freeze detection and export sampled thumbnails for human review.

detect_clippingA

Measure actual composition text bounds and clipping ancestors in Chrome at each scene midpoint; excludes text inside screenshots/video. Temporary QA files are cleaned up.

inspect_audio_levelsB

Measure actual FFmpeg peak/mean levels and report clipping risk.

validate_exportB

Fully decode exported media and verify codec and optional dimensions.

generate_quality_reportD

Persist measured decode/stream/audio checks and explicit manual review requirements.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.7/5.0

Scored across 41 tools

Disambiguation2/5

Several clusters have unclear boundaries despite verbose descriptions: render_video vs export_video vs export_project vs generate_remotion_project all appear to produce artifacts from a timeline, and export_project vs generate_remotion_project read as near-duplicates. Similarly validate_timeline / validate_export / inspect_render / analyze_rendered_frames form an overlapping QA/validation cluster, and generate_storyboard / create_scene_plan / create_motion_scene / generate_remotion_project are four plausible entry points for 'build a timeline'. An agent would need to read full descriptions to avoid misselection.

Naming Consistency5/5

Every tool follows a snake_case verb_noun pattern (import_audio, capture_page, validate_export, create_transition, etc.), with verbs drawn from a coherent vocabulary across the pipeline stages. The only nit is near-identical names like generate_voiceover vs generate_voiceover_script, but the structural convention itself is uniform.

Tool Count2/5

41 tools is well above the comfortable range for a single server and the surface reads as several sub-servers bolted together (project analysis, browser capture, timeline authoring, audio, rendering, QA/export). Many tools are thin single-step operations that could be consolidated into a handful of parameterized tools.

Completeness4/5

The lifecycle is unusually thorough: analysis, evidence capture, creative planning, timeline authoring, rendering, validation, QA reporting and export are all represented. Gaps are minor but real — no tools to update/reorder/remove existing scenes or shots, no project listing, and no subtitle/text-overlay burn-in step.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues