@demostudio/mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEMOSTUDIO_API_KEY | Yes | Your DemoStudio API key |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_videoA | Generate a short-form demo video (Instagram Reel / TikTok / YouTube Shorts) from a text prompt. DemoStudio writes the script, renders each scene with AI video or motion-graphic templates, adds voiceover and music, and returns a project URL where the user can preview and export. Use this when the user wants to create a promotional video, product demo, or UGC-style ad. |
| get_video_statusA | Check the status of a video project by its ID. Returns current status, scene build progress, and the final exported video URL once export is complete. |
| list_capabilitiesA | List all scene types and Remotion motion-graphic templates available in DemoStudio. Call this before writing a detailed prompt so you can reference the correct scene types and template names. Returns all 5 scene types (cinematic, canvas, slideshow, remotion, video) and all 17 Remotion templates. |
| create_scheduleA | Set up the DemoStudio Agent to automatically generate and export a new video on a recurring schedule (daily, weekly, biweekly, or monthly) from a brand Knowledge Base. The Agent varies the hook angle and structure each run to avoid repetition. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: scheduling recurring videos, generating one-off videos, checking status, and listing capabilities. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (create_schedule, generate_video, get_video_status, list_capabilities).
With 4 tools covering generation, scheduling, status, and capabilities discovery, the count is well-scoped for a video generation server.
Covers core workflows (create, schedule, check status, list capabilities). Minor gap: no tool to update or delete schedules, but the surface is sufficient for basic use.