sync. labs MCP Server — Use sync. labs from Claude, ChatGPT & AI Assistants via MCP

What Is the Sync Labs MCP Server?

The Sync Labs MCP server is an open-source Model Context Protocol server that connects AI assistants — including Claude, ChatGPT, Claude Code, Codex, Cursor and VS Code — to the Sync Labs lipsync API. Instead of writing code or using the Studio, describe what you want in plain English and your AI assistant handles the API calls for you.

Which AI Clients Support the Sync Labs MCP Server?

Sync Labs hosts the MCP server at https://mcp.sync.so/mcp. Any client that supports remote MCP servers connects to it and signs you in with your Sync Labs account through OAuth. You don’t need to install anything or create an API key.

How Do I Set Up the Sync Labs MCP Server?

Point your client at https://mcp.sync.so/mcp and sign in to Sync Labs when it asks. Every client below uses the same hosted server.

claude mcp add --transport http sync https://mcp.sync.so/mcp

codex mcp add sync --url https://mcp.sync.so/mcp
codex mcp login sync

{
  "mcpServers": {
    "sync": { "url": "https://mcp.sync.so/mcp" }
  }
}

{
  "servers": {
    "sync": { "type": "http", "url": "https://mcp.sync.so/mcp" }
  }
}

Choosing Organizations

Claude and ChatGPT connect to every organization you belong to as soon as you sign in, with the organization active in Studio as the default. Other clients ask which organizations the connection can work in: every one starts ticked, so untick any you want to leave out, and set default next to another ticked one makes it the default. The agent works in the default organization unless you ask it to switch, and paid generations use that organization’s credits or usage.

• Switch during a conversation: ask the agent to work in another organization it is connected to. It lists them with organizations_list and switches with organizations_select, and you can ask which organization it’s working in at any time.
• Add an organization later: connect again (and tick it, for clients that ask). Switching organizations in Studio doesn’t change an existing connection.
• See or remove a connection: each organization lists the connection under Settings → Agents & MCP in Studio, where you can disconnect it from that organization alone.

An API key always works in the organization it was created in and can’t switch.

Local Server for Scripts, CI and Other Clients

Use the hosted server whenever your client supports remote MCP servers. Run the server locally only for clients without remote MCP support, or for scripts, CI and other unattended agents. The local server needs Node.js 22.19+ and runs over stdio from the @sync.so/mcp-server package.

For unattended use, pass a Sync Labs API key from your dashboard settings (see the authentication guide):

claude mcp add sync -e SYNC_API_KEY=your-api-key -- npx -y @sync.so/mcp-server@latest

Or in a client’s JSON config:

{
  "mcpServers": {
    "sync": {
      "command": "npx",
      "args": ["-y", "@sync.so/mcp-server@latest"],
      "env": { "SYNC_API_KEY": "your-api-key" }
    }
  }
}

Without SYNC_API_KEY, the server signs you in on its first run instead: open the URL it prints and enter the code. It saves the token to ~/.config/sync/mcp-credentials.json.

npm releases ship separately from the hosted server and can lag behind it. @latest makes npx fetch the newest release when the client restarts the server; without it, npx can keep running an old cached copy.

What Can I Do with the Sync Labs MCP Server?

Once connected, you can create lipsync videos, check generation status, estimate costs, and manage assets — all through natural language. Here are example prompts you can try with your AI assistant:

• “Create a lipsync video with this video URL and audio URL”
• “Check the status of generation gen-abc123”
• “List available Sync Labs models”
• “Show me my recent generations”
• “How much would it cost to generate a 30-second video?”
• “Get the details of my latest completed generation and give me the output URL”
• “Estimate the cost for a 45-second lipsync video, then create it if it’s under $1”
• “Which organization and plan am I on, and how much do I have left to spend this month?”

The hosted server offers the same curated tools to every client; the ChatGPT plugin adds its embedded Studio and leaves out a few, as its guide explains. These are the main ones. The server README lists them all. Tools are named <noun>_<verb>. Earlier names such as generate_get-generation and create-lipsync still work as aliases for now, but new setups should use the names below.

To translate and dub, review a combined estimate with generations_estimate-cost and workflow: "translate-and-dub", create it with dubbing_create, then poll the returned ID with generations_get. create-translate-and-dub remains an older alias.

Many Jobs vs Batch

jobs_create-many runs one create tool, such as lipsync_create, dubbing_create or dialogue-videos_create, once per item, up to 50 at a time. Each job has the same limits and billing as a single call, so it works on any plan, within your plan’s concurrency limit. It isn’t in the ChatGPT plugin yet. The Batch API is a separate queued pipeline for large runs of 20 to 500 generations that can wait hours, and needs the Scale plan or above.

Sync Labs MCP Server vs SDK vs REST API

The Sync Labs MCP server is one of three ways to integrate with the Sync Labs API. Choose the approach that best fits your workflow:

The Sync Labs MCP server is ideal when you want to explore the API, prototype workflows, or create lipsync videos without writing code. For production applications, the Sync Labs SDKs or REST API give you full programmatic control.

CLI Options

The local Sync Labs MCP server accepts the following options. The hosted server needs none of them.

Programmatic Usage

You can also use the Sync Labs MCP server as a library in your own applications. This is useful when you want to embed Sync Labs’ MCP tools into a custom AI agent or multi-tool pipeline:

import { createSyncMcpServer, resolveConfig } from '@sync.so/mcp-server';
const config = resolveConfig({ apiKey: 'your-key' });
const server = await createSyncMcpServer(config);

Programmatic clients use the same tool generation and client-profile filtering. Inspect the connected server’s tool list for the operations available to your agent.

Troubleshooting

npm install -g @sync.so/mcp-server

{
  "mcpServers": {
    "sync": {
      "command": "sync-mcp",
      "args": [],
      "env": {
        "SYNC_API_KEY": "your-api-key"
      }
    }
  }
}

{
  "mcpServers": {
    "sync": {
      "command": "node",
      "args": ["node_modules/@sync.so/mcp-server/dist/cli.js"],
      "env": {
        "SYNC_API_KEY": "your-api-key"
      }
    }
  }
}

Frequently Asked Questions

Related Resources

• Quickstart — get started with the Sync Labs API
• Authentication — API keys for the local server, SDKs and REST API
• SDKs — use official Python or TypeScript SDKs
• GitHub: @sync.so/mcp-server — source code and issues