motionvault
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MOTIONVAULT_BASE_URL | No | One HTTP(S) origin for the MotionVault website/source API. Remote origins require HTTPS. No credentials, paths, query strings, or arbitrary source URLs. For the live website set MOTIONVAULT_BASE_URL=https://motionvault.site; for local development the source API defaults to http://localhost:5188. | |
| MOTIONVAULT_CATALOG_PATH | No | Optional absolute path to another validated catalog snapshot. | |
| MOTIONVAULT_MCP_BIND_HOST | No | The host the local HTTP service binds to (default 127.0.0.1). Deployments may explicitly set MOTIONVAULT_MCP_BIND_HOST=0.0.0.0 only with exact MOTIONVAULT_MCP_ALLOWED_HOSTS. | |
| MOTIONVAULT_MCP_ALLOWED_HOSTS | No | Comma-separated exact hosts permitted by the local HTTP service's Host checks; required when MOTIONVAULT_MCP_BIND_HOST is set to 0.0.0.0. | |
| MOTIONVAULT_MCP_ALLOWED_ORIGINS | No | Comma-separated exact browser origins permitted by the local HTTP service. Requests without Origin, such as ordinary MCP clients, remain supported. |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_templatesB | Search original template, style, background, gradient or UI libraries using words and bounded filters. |
| get_templateC | Get one original template and precise media capabilities. |
| compare_templatesB | Compare 2–5 templates by engine, source media, style and formats. |
| get_build_promptC | Return an original template build prompt with bounded user customization. |
| get_source_linksB | Get public source, playground, demo and license links without fetching account data. |
| get_template_sourceB | Fetch complete public standalone HTML and asset manifest from the one configured MotionVault origin; 8s/1MB limit. |
| get_asset_manifestB | List original public poster/video/font asset URLs and ZIP paths; no remote media download. |
| create_cinematic_briefC | Compose a concrete photographic/CG asset brief and implementation acceptance criteria. |
| plan_storyboardC | Create mechanism-specific four-chapter shots with precise time/frame/progress ranges. |
| build_motion_timelineB | Allocate weighted beats to exact seconds, frame ranges and normalized progress. |
| get_design_tokensC | Generate viewport-specific readable typography, composition tokens and CSS variables. |
| get_easing_curveC | Calculate a sampled cubic-bezier curve using time-axis inversion, plus CSS easing. |
| analyze_contrastB | Calculate WCAG contrast for two opaque hex colors and normal/large text thresholds. |
| plan_responsive_cropC | Compute object-fit cover scale, crop offsets and object-position for a desired subject position. |
| get_export_checklistB | Return format-specific packaging and playback checks grounded in a selected template. |
| generate_scroll_scaffoldC | Generate complete original pinned native-scroll HTML with reversible chapter states, pause and reduced motion. |
| generate_glsl_shaderC | Generate a working original WebGL fragment/vertex shader and standalone pointer-reactive HTML. |
| validate_motion_specB | Check declared typography, source-media claims, export assets and timing for concrete implementation mistakes. |
| get_design_systemC | Get an original style system, declared tokens and DESIGN.md without copying a reference library. |
| get_asset_sourceC | Return bundled original asset source, or explicit CSS variables generated from declared style tokens. |
| generate_paletteB | Generate a tonal HSL palette from one seed and calculate actual opaque contrast pairs. |
| generate_type_scaleC | Calculate a modular type scale and fluid CSS across explicit viewport endpoints. |
| generate_spacing_scaleC | Build a consistent spacing rhythm and responsive CSS without mixing unitless lengths. |
| compare_design_assetsB | Compare 2–5 bundled style/UI/background assets, including actual token differences. |
| inspect_htmlA | Inspect supplied HTML source for structural counts, resource references, duplicate IDs and broken anchors; never execute it. |
| check_accessibility_markupB | Find concrete semantic source signals: language, title, headings, image alternatives, labels and empty controls. |
| check_motion_accessibilityB | Review declared motion plus supplied HTML for reduced-motion, pause and scroll-safety signals. |
| analyze_performance_budgetB | Sum supplied resource bytes by kind and compare explicit initial-load and total budgets. |
| validate_asset_manifestB | Check ZIP-relative paths, duplicate names, supplied packaged files, resource origins and license gaps. |
| audit_dependenciesC | Review supplied dependency versions and recorded license evidence for source redistribution. |
| review_licensingC | Triage per-asset evidence for end-project versus library redistribution; preserve restrictive source boundaries. |
| check_media_provenanceB | Compare supplied SHA-256 evidence and provenance requirements without claiming credential-chain verification. |
| plan_launch_preflightB | Build a release gate table from explicit observed evidence; unknown checks never become passes. |
| verify_template_sourceC | Fetch the configured public source endpoint and return its digest, resource findings and catalog media consistency. |
| plan_visual_qaC | Create exact five-progress capture cases across responsive viewports with media-specific expectations. |
| build_reduced_motion_planB | Map declared effects to meaningful still/low-motion alternatives and implementation hooks. |
| generate_responsive_layoutC | Generate original container-responsive CSS for an editorial hero and useful content grid. |
| generate_design_documentC | Create an original DESIGN.md from structured colors, typography, spacing and explicit component rules. |
| list_agent_workflowsA | Discover six reusable specialist role guides and their real tool dependencies; does not spawn agents. |
| get_agent_workflowB | Get a concrete specialist workflow, deliverables and relevant tools without starting background execution. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| build_cinematic_template | Begin an original cinematic template with media-first framing and complete source delivery. |
| review_motion_template | Review a declared template against cinematic composition and delivery requirements. |
| plan_product_film | Plan an authored person-to-product-to-macro-to-action cinematic sequence. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| template-catalog | Bundled public original template metadata and build prompts. |
| cinematic-guidelines | Concrete framing, typography, media truth and visual verification rules. |
| server-capabilities | Actual tools, skills, workflow guides, limits and supported scope. |
TDQS
Scored across 40 tools
Descriptions are precise, but the 40-tool set contains overlapping clusters: get_template_source and verify_template_source both hit the same configured source, while get_design_system, generate_design_document, and get_design_tokens all produce design tokens or DESIGN.md artifacts. plan_storyboard and build_motion_timeline also both allocate precise time/frame ranges, creating plausible misselection despite mostly clear individual purposes.
All 40 tools use snake_case with a predictable verb_noun convention (get_, generate_, validate_, plan_, check_, analyze_, build_, compare_, etc.). The naming is consistent across every tool, making the set easy to scan structurally.
40 tools is well beyond the typical 3–15 well-scoped range and feels heavy for a single MCP server, with many narrow validation, planning, and generation helpers. The large count increases discovery and selection burden even though some tools are grouped by domain.
The surface covers design tokens, asset inspection, motion planning, shader/scroll generation, accessibility, performance, licensing, provenance, launch preflight, and visual QA, which is broad. Minor gaps remain: no direct template CRUD, no actual media/export packaging execution, and no unified build pipeline, but most workflows have supporting tools.