ClipACanvas
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLIPACANVAS_FFMPEG_EXE | No | Path to FFmpeg executable (optional, auto-detected if not set) | |
| CLIPACANVAS_MAX_DURATION | No | Maximum render duration in seconds (optional, default: 12) | |
| CLIPACANVAS_BROWSERS_PATH | No | Path to Playwright browsers directory (optional, auto-detected if not set) |
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": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| render_videoA | Render HTML, CSS, and JavaScript code to an MP4 video using Chromium (headless) and FFmpeg. Supports CSS animations, WAAPI, SVG, and canvas animations. Returns the video as base64-encoded MP4. |
| render_video_to_fileA | Same as render_video but saves the resulting MP4 directly to a file path on disk instead of returning base64. Useful for integrating with other tools or when dealing with large videos. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| FFmpeg Configuration | FFmpeg path and version info |
| Render Options | Default render options |
TDQS
Scored across 2 tools
The tools are clearly differentiated by their output method (base64 vs file), and descriptions state the difference explicitly. However, the core functionality is identical, which could cause confusion if an agent doesn't read carefully.
Both tools follow a consistent pattern: 'render_video' base name with a suffix '_to_file' for the file variant. The naming is clear and predictable.
With only two tools, the server feels thin for a video rendering service. While it covers the basic render operation, additional tools for preview or status would make it more robust.
The server only offers rendering with two output formats. There are no tools for checking render status, managing rendered files, or handling different video settings, which are notable gaps.