Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y [email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
claude mcp add lipdub-mcp -- npx -y lipdub-mcp@0.1.3รันในเทอร์มินัล
{ "mcpServers": { "lipdub-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดGive your AI agent the ability to lip-sync video.
LipDub 2 makes a person in a video appear to speak a different audio track, with matched lip movement. This is an MCP server that exposes it to Claude, Cursor, Gemini CLI, Codex, VS Code, and any other MCP-compatible client.
LipDub 2 does not translate, transcribe, or generate speech. You bring the audio. If you want a video dubbed into another language, generate that audio first with a text-to-speech or voice-cloning tool, host it at a public URL, and pass that URL. It pairs naturally with a text-to-speech server for that first step.
You: Lip-sync https://example.com/keynote.mp4 to https://example.com/spanish.mp3
Claude: I'll use LipDub 2 for that. This will charge credits to your LipDub
account and can't be refunded — shall I go ahead?
You: yes
Claude: Started — render_id rnd_88213. A clip this length takes a few minutes; I'll wait.
...
Done. Here's your video: https://… (link expires, so grab it soon)
Sign in at app.lipdub.ai.
Open Settings → API Keys: app.lipdub.ai/settings/api-keys
You must be an Owner or Admin on the account. Other roles are redirected to the dashboard with no explanation. If that link bounces you, ask an Owner or Admin on your team to generate the key for you.
Generate a key and copy it.
One key per user. LipDub issues a single API key per user, and generating a new one replaces the old one. If your account already uses its key for another integration, generating a fresh key will break it. Reuse the existing key, or use a separate Owner/Admin account for agent work.
Nothing to install: npx fetches it on first run.
claude mcp add lipdub --env LIPDUB_API_KEY=your_key_here -- npx -y lipdub-mcp
{
"mcpServers": {
"lipdub": {
"command": "npx",
"args": ["-y", "lipdub-mcp"],
"env": { "LIPDUB_API_KEY": "your_key_here" }
}
}
}
The file lives at ~/Library/Application Support/Claude/claude_desktop_config.json on
macOS, and %APPDATA%\Claude\claude_desktop_config.json on Windows. Restart Claude
Desktop after editing it.
{
"mcpServers": {
"lipdub": {
"command": "npx",
"args": ["-y", "lipdub-mcp"],
"env": { "LIPDUB_API_KEY": "your_key_here" }
}
}
}
{
"inputs": [
{ "type": "promptString", "id": "lipdub-key", "description": "LipDub API Key", "password": true }
],
"servers": {
"lipdub": {
"command": "npx",
"args": ["-y", "lipdub-mcp"],
"env": { "LIPDUB_API_KEY": "${input:lipdub-key}" }
}
}
}
This pattern keeps the key out of a file you might commit. Given that LipDub issues one key per user, that matters more here than it does for most servers.
{
"mcpServers": {
"lipdub": {
"command": "npx",
"args": ["-y", "lipdub-mcp"],
"env": { "LIPDUB_API_KEY": "your_key_here" }
}
}
}
[mcp_servers.lipdub]
command = "npx"
args = ["-y", "lipdub-mcp"]
env = { LIPDUB_API_KEY = "your_key_here" }
git clone https://github.com/marzvfx/lipdub-mcp.git
cd lipdub-mcp
npm ci && npm run build
Then use "command": "node", "args": ["/absolute/path/to/lipdub-mcp/dist/index.js"]
instead of the npx pair above. Needs Node 20+; ./manage.sh build does the same
inside a container if you have no Node.
First confirm the server itself runs:
npx -y lipdub-mcp --version
Then ask your agent: "check my LipDub connection". It should reply with your
account id. If it asks you to set an API key, the key is not reaching the server.
Check the env block above and restart the client.
There is a smoke test that drives the published server exactly as a real MCP client does, so a pass means the thing you installed actually works. No clone:
LIPDUB_API_KEY=your_key_here npx -y lipdub-mcp --smoke
That checks the handshake, the tool list and your API key. It renders nothing and costs nothing.
To exercise the whole flow, including a real render. This spends credits:
LIPDUB_API_KEY=your_key_here npx -y lipdub-mcp --smoke --render \
--video=https://example.com/speaker.mp4 \
--audio=https://example.com/speech.mp3
It starts the render, waits for it, and prints the download link.
If you already have assets uploaded to LipDub, pass their ids instead of URLs with
--video-id=<shot id> --audio-id=<upload id>, which helps when you have nowhere public
to host them. If a run is interrupted, --render-id=<id> re-attaches to the render
already in flight rather than paying for a second one.
From a git checkout, npm run smoke is the same command.
There is also a lipdub_quick_dub prompt (a slash command in clients that support
prompts) and two reference resources, lipdub://guide/quickstart and
lipdub://guide/troubleshooting.
Both inputs are public URLs, not local file paths, and the link must return the media file itself.
YouTube is the exception: youtube.com, youtu.be and youtube-nocookie.com are
resolved for you, so a normal watch URL works as video_url.
These do not work: Google Drive and Dropbox share pages, anything behind a login, and expired links.
For your own files:
# Amazon S3 — a time-limited direct link
aws s3 presign s3://your-bucket/keynote.mp4 --expires-in 3600
# Google Cloud Storage
gcloud storage sign-url gs://your-bucket/keynote.mp4 --duration=1h
# Any web server
scp keynote.mp4 you@yourserver:/var/www/html/
# → https://yourserver/keynote.mp4
Why URLs and not local files? A URL-based render is one API call. The upload-a-local-file path is several calls against endpoints that are rate-limited to roughly ten requests an hour, which works out at about two local-file renders per hour on the entry plan. Keeping this server URL-only also means it behaves identically wherever it runs. Local-file support may arrive later behind an opt-in.
Rendering takes several minutes for a short clip, and longer for longer videos, because generation time scales with the length of the source. LipDub also waits up to 15 minutes to download your two source files before giving up, so slow hosting shows up as a timeout rather than a render.
Renders consume credits from your LipDub account and cannot be refunded; cost scales with the length of the source video, so shorter clips cost less.
Checking status is free and is not rate-limited, so poll as often as you like.
Your credit balance is not available through the API; see app.lipdub.ai.
lipdub_create_render is the only tool that spends money. By default it refuses to run
until the agent passes confirm_spend, which forces it to state the cost to you first.
The server also stops after 5 renders per session.
These are usability guardrails, not security controls. Anything calling the API directly bypasses them.
Full API documentation: lipdub.readme.io
https://api.lipdub.ai, and is never written to disk, logged, or included in any
tool result. It is redacted from every log line and error message.LipDub 2 generates synthetic video of real people. By using it you warrant that you have the rights and consent necessary for the likeness and the voice in your source material. Do not use it to impersonate anyone without their permission, to create misleading content about real people, or for anything prohibited by LipDub's terms.
Found a vulnerability? See SECURITY.md. Please do not open a public issue, and never paste an API key into one.
Tool names are a public contract and will not change. New capability arrives as new tools; schema changes are additive. See CHANGELOG.md.
MIT. This licence covers this client. LipDub itself is a commercial service governed by its own terms.
MCP server for LipDub 2 — make a person in a video appear to speak a different audio track, with matched lip movement.
{ "mcpServers": { "lipdub-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Lipdub ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-14 MCP server for LipDub 2 — make a person in a video appear to speak a different audio track, with matched lip movement.