Show the real command
Developers trust what they can copy. Put the exact install or connect command on screen, the same as in your docs, not a simplified one that will not run.
Explainer videos for developer tools, APIs and MCP servers
A developer tool explainer shows what your API, SDK, CLI or MCP server does and how to start, with the real commands on screen. Put your docs link in a Voom prompt: Voom reads the page, shows the setup steps and code from it, and adds a calm voice-over, original music and optional captions. Developers see what they will type before they open the docs.
Prompt Explain our MCP server in 45 seconds, for developers: add the connector, sign in, then ask Claude or Cursor for a whiteboard video in chat. Show the setup as the real commands from our docs. Calm, exact, no hype. Link: trychasca.com/docs/mcp
How do you make a developer tool explainer with Voom?
- 01
Paste your docs link
Use the quickstart or setup page. Voom reads its headings, commands and text, and takes your colours and fonts. Add screenshots of code blocks with Images for exact frames.
- 02
Name the path to show
Install, connect, first result. Write the commands that must appear and the result the viewer should see.
- 03
Ship it with the docs
16:9 for the docs page, the README and YouTube; 1:1 for X and LinkedIn. Check every command on screen against your docs before you publish.
How to explain a developer tool on video
Shortest path to a result
The best developer explainers show the shortest path from nothing to something working: one command, one call, one result. Leave the rest to the docs and end on where they are.
Code is read, not watched
Hold each command on screen long enough to read, and mark the one part that matters, such as the URL or a flag. Ask for this in your prompt: hold each command and highlight the address.
Where it falls short
Voom shows code as designed frames, not as a live terminal or an editor recording. For a full coding tutorial, record your screen; use a Voom explainer for the docs page, the README and the launch post.
Prompts to start from
- Example prompt
A 45-second explainer for developers from our docs link: what our API does, the install command, the first call and its result. Real code on screen, calm voice.
Use this prompt - Example prompt
Explain our MCP server in 45 seconds: add the connector, sign in, ask for a result in chat. Show the setup as the real commands from our docs.
Use this prompt - Example prompt
A 30-second square video for X announcing our new CLI: the install line, one command, the output.
Use this prompt - Example prompt
A 60-second explainer of how our SDK handles retries and rate limits, one diagram per idea, for our docs page.
Use this prompt
Why developer tools explain with Voom
-
Commands from your docs
Voom reads your docs page and shows its commands and steps on screen.
-
Facts checked
Facts Voom keeps from your page must appear there word for word.
-
Your docs’ look
Colours and fonts from your site, code in your monospace.
-
Every channel a launch needs
16:9 for docs and YouTube, 1:1 for X, 9:16 for Shorts.
What does a developer tool explainer cost?
A 45-second explainer uses 15 credits, about $0.78 on Pro. Your first video, up to 30 seconds, is free, with a small watermark.
Questions, answered
Pick the shortest path to a first result: install, authenticate, one call, one response. Put your docs link and those steps in a Voom prompt, and Voom writes the script, shows each command on screen, adds a voice-over, music and captions, and renders an MP4 for your docs page and launch posts.
Yes. With your docs link, Voom shows the commands and steps your page contains, and you can add screenshots of code blocks with Images. Check every command in the finished video against your docs before you publish, because code on screen has to run when someone copies it.
Yes. The sample film on this page explains an MCP server from its setup page: the connector address, the Claude Code command and what you can then ask for in chat. Write which clients you support and the steps to connect, and Voom shows each one.
Thirty to sixty seconds for a quickstart: what it is, how to connect, one result. A deeper walkthrough of a feature can run 90 seconds. Voom’s free video runs up to 30 seconds, Pro up to 90 seconds and Business up to 3 minutes.
Not yet. Voom has no public API, MCP server or CLI; you make videos in the app at madewithvoom.com. The sample film on this page explains another company’s developer tool, made from its public docs.
Keep reading
-
What to make
How to make a product demo video that shows the product, not a tour
How to make a product demo video: a five-part structure, the right length for each place it plays, real screens versus redrawn ones, and how to keep every number true.
4 min read
-
What to make
Explainer video script: a template, word counts and three real scripts
An explainer video script template with word counts for 30, 60 and 90 seconds, five beats that work for any topic, and three full scripts with their timings.
7 min read
-
What to make
How to make an explainer video: a step-by-step guide with real examples
How to make an explainer video that people follow to the end: pick one idea, size the script to the length, give every line a picture, then add voice and music.
7 min read
Your first video is one sentence away.
Free to start. No card, no timeline, no stock templates.
Make a developer explainer