Use DemoVexa from Claude (MCP)
Connect Claude Desktop or Claude Code to DemoVexa on your computer, then ask Claude to make, check and render your videos.
You can ask Claude to make your videos for you. Connect Claude Desktop or Claude Code to DemoVexa once, then ask in plain words. Claude talks to DemoVexa on your computer through MCP (the Model Context Protocol), and DemoVexa makes the video as if you'd clicked the buttons yourself.
For example:
- "Make a feature-launch video for the invoice export I just shipped."
- "What's the status of my latest video?"
- "Render the vertical version."
- "Give me the LinkedIn post for Data Rooms."
- "Suggest three video ideas for the Contacts module."
Note
It works only on a computer where DemoVexa is installed and set up. Claude doesn't make videos on its own: it asks DemoVexa to.
#Connect Claude Desktop
- Install Claude Desktop, sign in and open it once.
- In DemoVexa, go to Settings → Connect to Claude. You can also use Help → Use DemoVexa from Claude… in the menu bar.
- Click Add to Claude Desktop and confirm. DemoVexa adds itself to Claude Desktop's settings file and keeps everything else in it. It saves a backup next to the file first.
- Quit Claude Desktop completely and open it again. On a Mac, press ⌘ Q; closing the window isn't enough.
- Ask Claude something, such as "What videos do I have in DemoVexa?" Claude asks before it uses a DemoVexa tool the first time.
To disconnect, click Remove on the same page, then restart Claude Desktop.
Tip
If Claude Desktop's settings file has a mistake in it, DemoVexa won't change it. It shows the text to add by hand instead.
#Connect Claude Code
- In DemoVexa, go to Settings → Connect to Claude.
- Under Claude Code, click Copy next to the command.
- Paste it into a terminal (PowerShell on Windows) and press Enter. It starts with
claude mcp addand adds DemoVexa for every project on your computer. - Start a new Claude Code session.
Claude Code is handy right after you ship a feature: ask "make a launch video for what we just built" and it passes a summary of the change, the changed files and the commit messages to DemoVexa, so the video shows the right screens.
#Other MCP apps
Any app that can run a local MCP server can use DemoVexa. Copy the JSON under Other MCP apps on the same page into that app's MCP settings.
#What Claude can do
| Tool | What it does |
|---|---|
| List workspaces | Shows your products and which one is open |
| List projects, get a project | Shows your videos, where each one is, its script and scene plan |
| List ideas | Shows Claude's suggestions and your creation list |
| Make a video | Takes an idea from brief to finished video: script, voiceover, scene plan, build, renders, posts and covers |
| Make a video from a code change | Turns a change you just shipped into a feature-launch video |
| Check progress | Shows the current step, a rough percentage, render progress, errors and what's next |
| Approve the scene plan | Starts the build after you've checked the plan |
| Revise | Changes the built video with a note, or rewrites the script |
| Render | Renders formats (vertical, landscape, square), with a normal, green or transparent background |
| Get posts | Gives the LinkedIn, X, Instagram, Facebook, Reddit and YouTube posts and the blog post |
| Get files | Gives the paths of the MP4s, covers, voiceover and marketing kit on your computer |
| Suggest ideas | Asks Claude for new video ideas from your app's code and recent changes |
| Open in DemoVexa | Opens a video in the app, to edit it by hand |
Claude can't delete anything or change your settings.
A video takes 20 to 45 minutes. Claude starts it, then checks on it about once a minute while you wait, or whenever you ask. If you want to review the scene plan before the build, say so ("let me check the plan first"): the video then waits for your approval.
#Costs and limits
Videos made from Claude count the same as videos you start in DemoVexa:
- Each new video uses one video from your plan's monthly allowance, and each format you render uses one render. See Plans and usage.
- Each video Claude makes counts toward your plan's videos a month, like one you start in the app (the free trial included).
- Writing, planning, building and suggesting ideas use your Claude account, and voiceovers use your ElevenLabs characters, as usual.
- Reading things (lists, progress, posts and file paths) costs nothing.
#Privacy
Everything stays on your computer. Claude Desktop or Claude Code starts a small helper that talks only to DemoVexa on this computer. Nothing goes through DemoVexa's servers.
Only the apps you connect can use it. DemoVexa keeps a private access key in its data folder, and web pages in your browser can't use the connection. If you think something else has the key, click Reset access: your Claude setup keeps working, and anything that copied the old key stops.
What Claude Desktop or Claude Code sends to Anthropic is your conversation, including what DemoVexa answers (names of your videos, scripts and posts), as with anything else you ask Claude.
#Troubleshooting
| Problem | What to do |
|---|---|
| "Open DemoVexa on this computer first" | Open DemoVexa and ask again. Claude tries to open it by itself, but it has to be installed and set up first. |
| Claude doesn't show DemoVexa's tools | Quit Claude Desktop completely and open it again: it reads its settings only when it starts. In Claude Code, run claude mcp list to check that DemoVexa is there. |
| "A different data folder" or "Wrong access token" | DemoVexa moved or was reinstalled. Click Add to Claude Desktop (or Update in Claude Desktop) again, or run the Claude Code command again, then restart Claude. |
| Out of videos or renders | Videos made from Claude use your monthly allowance. Check Settings → Account. |
| A video failed | Ask Claude for its status to see the error, then open it in DemoVexa and click Retry. |
Last updated · View as Markdown
Something unclear or missing on this page? Tell us
