Mjudio speaks the Model Context Protocol. Point Claude, Cursor or VS Code at the copy of Mjudio running on your Mac and ask for a video: it picks a template, takes your song, writes the titles and lyrics, renders the file and hands it back.
Updated 9 September 2026
Everything stays on your Mac. The MCP endpoint is the same loopback
server the Automation API uses. It is off until you switch it on in
Mjudio ▸ Settings ▸ Automation, it answers only on 127.0.0.1,
and every request carries a token that screen shows you. Your audio is never uploaded
anywhere: rendering happens on your own GPU.
Claude Desktop will not connect to a plain http:// address, even a local one,
so Mjudio ships a small extension that bridges the gap. Download it, double-click it, and
Claude Desktop installs it:
Then, before you ask for anything:
The extension asks for an address and a token, and both can be left blank: it reads them from Mjudio's own configuration file. Fill them in only if you changed the port.
These connect to the address directly, so there is nothing to install. In Mjudio ▸ Settings ▸ Automation ▸ Agents, press Copy setup and pick your client. That puts a ready-made snippet on the clipboard with your own port and token already filled in.
Claude Code — paste the command into a terminal:
claude mcp add --transport http mjudio http://127.0.0.1:8787/mcp \
--header "Authorization: Bearer YOUR_TOKEN"Cursor — paste into ~/.cursor/mcp.json:
{
"mcpServers": {
"mjudio": {
"url": "http://127.0.0.1:8787/mcp",
"headers": { "Authorization": "Bearer YOUR_TOKEN" }
}
}
}VS Code — paste into .vscode/mcp.json in your workspace:
{
"servers": {
"mjudio": {
"type": "http",
"url": "http://127.0.0.1:8787/mcp",
"headers": { "Authorization": "Bearer YOUR_TOKEN" }
}
}
}Your token changes whenever you press Regenerate on the Automation screen. If a client suddenly reports 401, copy the setup again.
Mjudio binds loopback and nothing else, on purpose. If you genuinely need an assistant on another machine to reach it, tunnel to it over SSH rather than exposing the port:
ssh -N -L 8787:127.0.0.1:8787 you@your-mac.localThe assistant then connects to http://127.0.0.1:8787/mcp on its side,
and the traffic is carried by SSH. Nothing about Mjudio's own binding changes.
Mjudio is sandboxed: it can open the files you pick and no others. That is why an assistant cannot simply name a path on your disk and have Mjudio read it.
To hand over a folder, open Settings ▸ Automation ▸ Shared folders, press Add and pick it. From then on an assistant may name files inside that folder and nowhere else, and it is where finished exports can be saved. Remove a folder on the same screen and the access goes with it.
If you are using the Claude Desktop extension, a file outside every shared folder can still be sent: the extension reads it and uploads the bytes. Shared folders are what make large files and finished exports practical.
Plain requests work. Some that do what you would expect:
~/Music/night-drive.m4a using a lo-fi template,
title it Night Drive by Test Artist, then export it at 1080p."| Area | What it covers |
|---|---|
| Projects | List, read, create, rename, change the shape, delete |
| Templates | List them, filter by category, apply one |
| Media | Attach a song, attach cover art, trim and fade |
| Text | Set the title and artist, add lyrics as plain text, .lrc or .srt |
| Chapters | Turn a pasted tracklist into chapters and a now-playing card |
| Export | Queue a render, poll it, list finished ones, save one to a shared folder |
Deleting a project is marked destructive, so a well-behaved client asks you first. Nothing an assistant does bypasses the app: it is the same code the buttons run.
An assistant gets exactly the plan you have. On the free plan a request for 4K comes back at 720p with a watermark, premium templates are refused, and the daily export allowance applies. Asking an assistant to "export in 4K without the watermark" does not change that — it is the same check the export sheet makes.
| What you see | What it means |
|---|---|
| "Mjudio is not answering" | Mjudio is not running, or Automation is still off in Settings. |
| 401, or "refused the access token" | The token has been regenerated. Copy the setup again. |
| "is not inside a shared folder" | Add that folder under Settings ▸ Automation ▸ Shared folders. |
| "open in an editor window" | The project is open in Mjudio and its autosave would overwrite the change. Close the window. |
| The tools never appear in Claude Desktop | Quit and reopen Claude Desktop after installing the extension. |
There is no assistant connection on iOS, and it would not be honest to imply otherwise. The server binds loopback, which on a phone means that phone — nothing on your Mac or your network can reach it — and iOS suspends the app the moment you switch away from it.
What does work on iOS is the Shortcuts app. Mjudio's actions appear there: create a video from a song, add lyrics, export. Those run on the device, and Siri can trigger them.