sync. labs

Name: sync. labs
Author: synchronicity-labs

by synchronicity-labsversion 0.2.4i★ –iComputer or cloud

Registry nameio.github.synchronicity-labs/mcp-server

Install

Overview

Description from the maker (original English)

Lipsync videos, dub them into other languages, make talking videos and open sync. Studio.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Other
You need to fill in: SYNC_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 3 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: SYNC_API_KEY, SYNC_MCP_TOOLSETS

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://mcp.sync.so/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "synchronicity-labs": {
      "command": "npx",
      "args": [
        "-y",
        "@sync.so/mcp-server"
      ],
      "env": {
        "SYNC_API_KEY": "your-value",
        "SYNC_MCP_TOOLSETS": "your-value"
      }
    }
  }
}

Run this in your terminal

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

Or run it on your computer

claude mcp add synchronicity-labs --env SYNC_API_KEY=your-value --env SYNC_MCP_TOOLSETS=your-value -- npx -y @sync.so/mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "synchronicity-labs": {
      "command": "npx",
      "args": [
        "-y",
        "@sync.so/mcp-server"
      ],
      "env": {
        "SYNC_API_KEY": "your-value",
        "SYNC_MCP_TOOLSETS": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "synchronicity-labs": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@sync.so/mcp-server"
      ],
      "env": {
        "SYNC_API_KEY": "your-value",
        "SYNC_MCP_TOOLSETS": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://mcp.sync.so/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

SYNC_API_KEY secret env
sync. API key from https://sync.so/settings/api-keys. Without one, the server starts a device login on first run.
SYNC_MCP_TOOLSETS env
Comma-separated toolsets to list: default, lipsync, dubbing, assets, projects, transcription, voices, admin or all. Defaults to the hosted server's tools without deletes or voice cloning.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account synchronicity-labs, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 84 ms (HTTP 401)
✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 32683 servers in this category
Published to the registry more recently than 99% of the other 32683 servers in this category
Basic checks equal to or better than 100% of the other 32683 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is sync. labs safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: SYNC_API_KEY

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.4) reached the registry today.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, MCP Server Autocad Lisp Helper

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

MCP Server Autocad Lisp Helper

by radwanalmsora

High-precision static analysis and debug server for AutoCAD AutoLISP (.lsp) files.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

sync. MCP server

Connect your AI agent to sync. to lip-sync videos, translate and dub them into other languages, clone voices, and manage assets and projects from a chat or a coding session.

sync. hosts this server at `https://mcp.sync.so/mcp`. You sign in with your sync. account, so there is nothing to install and no API key to copy. Every merge to this repository's main deploys there.

Connect your agent

ChatGPT

Open sync. in ChatGPT and connect your account. In ChatGPT, sync. Studio also opens inside the chat.

Claude (claude.ai and Claude Desktop)

Open Settings → Connectors and choose Add custom connector.
Name it sync. and set the URL to https://mcp.sync.so/mcp.
Click Connect and sign in to sync.

Claude Code

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

Then run /mcp in Claude Code, select sync and sign in. Add --scope user to use it in every project.

Codex

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

codex mcp login sync

Cursor

Add to .cursor/mcp.json in a project, or ~/.cursor/mcp.json for all projects:

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

Cursor asks you to sign in to sync. the first time it connects.

VS Code

Add to .vscode/mcp.json:

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

Other clients

Any client that supports remote MCP servers over Streamable HTTP with OAuth can use https://mcp.sync.so/mcp. The client registers itself, and you sign in to sync. in the browser.

The server is listed in the official MCP Registry as io.github.synchronicity-labs/mcp-server, so clients and directories that read the registry can find and add it. server.json is that listing.

Local server with an API key

For clients without remote MCP support, and for scripts and CI, run the server locally over stdio with a sync. API key:

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 starts a device login on first run: visit the URL it prints and enter the code. The token is cached at ~/.config/sync/mcp-credentials.json.

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

Update notice

At startup a local server asks the npm registry for the latest version, at most once a day (the answer is cached in ~/.config/sync/mcp-update-check.json). The check runs in the background with a two-second limit and never delays startup or a tool call; if it fails, nothing is shown. When a newer version exists, the server's instructions and the first tool result of the session tell the agent to ask you to restart with npx -y @sync.so/mcp-server@latest or switch to the hosted server.

To turn it off, set SYNC_MCP_UPDATE_CHECK=off or pass --no-update-check. It is also skipped when CI is set, and the hosted server never checks.

What to ask

Paste prompts like these into your agent. Asset IDs come from your sync. library. Links can be public media URLs or YouTube, TikTok, Instagram and Facebook videos.

Ask	What the agent does
"Lipsync video asset with audio asset ."	`lipsync_create` with the saved assets, then waits for the result
"Lipsync https://example.com/talk.mp4 to https://example.com/voiceover.wav."	`lipsync_create` with public URLs
"Translate https://www.youtube.com/watch?v=… to Spanish."	Imports the link with `assets_create`, quotes the cost, and after you confirm runs `dubbing_create`
"Make video asset say “thanks for watching” in a calm narrator voice."	Picks a voice with `voices_list`, quotes the script, then `lipsync_create` with `script`
"How many credits do I have left?"	`account_get-usage`
"What did my last generation cost?"	Finds it in history and reads `generations_get-costs`

Translation, dubbing, speech previews and voice clones are quoted and confirmed with you before they start.

Agent skills

Step-by-step workflows for these tools (lipsync, talking photos, dubbing, Edit Dialogue, campaigns, batches, troubleshooting and the API) are agent skills in synchronicity-labs/skills. Install them in any agent with npx skills add synchronicity-labs/skills. The ChatGPT and Codex plugin ships them from a pinned commit of that repository; see docs/chatgpt-plugin.md.

Tools

The hosted server exposes a curated set of tools to every client:

Area	Tools
Lip sync	`lipsync_create`, `lipsync_create-timeline`¹, `generations_estimate-cost`, `generations_get`, `generations_list`, `generations_get-continuation`, `generations_get-costs`, `models_list`
Translation and dubbing	`dubbing_create`, `dubbing_get-options`, `translation-previews_estimate`, `translation-previews_create`, `translation-previews_get`
Speech and voices	`speech-previews_create`, `speech-previews_get-options`, `speech-previews_get`, `voices_list`, `voices_clone`
Edit Dialogue	`dialogue_get-options`, `dialogue_upload-source`, `dialogue-transcriptions_create`, `dialogue-transcriptions_get`, `dialogue-previews_create`, `dialogue-previews_get`, `dialogue-videos_estimate`, `dialogue-videos_create`
Assets	`assets_create`, `assets_create-upload-url`, `assets_get`, `assets_list`, `assets_count`, `assets_get-download-url`, `assets_update`, `assets_delete`, `assets_get-playback-metadata`, `audio-trims_get`, `audio-trims_create`
Projects	`projects_create`, `projects_get`, `projects_list`, `projects_list-generations`, `projects_rename`
Batches	`batches_create`², `batches_get`², `batches_list`²
Account	`account_get-context`, `account_get-usage`, `organizations_list`, `organizations_select`

¹ Not offered to the ChatGPT app, whose embedded Studio has no timeline.

² Not in the ChatGPT app listing yet. A batch runs 20 or more independent generations (500 per batch by default), such as one campaign video localized into many languages. Where the account's plan doesn't include batch, the API answers 402 with requiredPlan and billingUrl, which the tools pass on.

Organizations with the matching feature also get scenes_detect (camera cuts in a video) and stems_separate (vocals and background audio), outside the ChatGPT app. They are in the lipsync and assets toolsets locally.

Clients with app support also get the tools behind the embedded Studio app: Studio views and drafts, the upload widget and app helpers. Those are clients whose MCP handshake name selects the ChatGPT or Codex app profile (openai-mcp, openai-mcp (Codex); see src/client-profile.ts). Other clients don't see these tools, and their calls to them are refused.

Local toolsets

The local stdio server can also offer a tool for every other public API operation in the OpenAPI spec, 65+ in all. By default it lists the hosted set above, without its admin tools (assets_delete and voices_clone), plus jobs_get and jobs_wait and the transcriptions_* tools, whose speaker face tracks feed lipsync_create-timeline clips.

To list more, set SYNC_MCP_TOOLSETS or pass --toolsets with a comma-separated list:

Toolset	Adds
`default`	The default above, so `default,admin` adds the admin tools to it
`lipsync`	Lip sync, timeline, Edit Dialogue, audio trim and batch tools, plus raw `generate_`, `generations_` and `dialogue-edits_*`
`dubbing`	Translation and dubbing tools, and the batch tools
`assets`	`assets_*` (except deletes) and the upload tools
`projects`	`projects_*` (except deletes) and `projects_rename`
`transcription`	`transcriptions_*`
`voices`	`voices_` (except cloning and deletes), speech previews and `tts_`
`admin`	Every delete (`assets_delete`, `projects_delete`, `generations_delete`, `voices_delete`) and `voices_clone`
`all`	Every tool, as before this option existed

Job, account and generation reads (jobs_get, jobs_wait, generations_get, account_get-context, organizations_list, organizations_select and similar) come with every selection. Naming toolsets replaces the default rather than adding to it. To get every tool back:

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

Unless it lists everything, the server's instructions tell the agent which toolsets are listed and how to get the rest, so it can ask you to restart the server with a wider set. The hosted server ignores this setting.

Tool workflows describes how the multi-step and paid tools behave.

Tool names follow one _ scheme (lipsync_create, generations_get). The names used before it (create-lipsync, generate_get-generation) still work for a deprecation period: calls through them run the same tool and add a one-line notice naming the new one. Tool names has the full old → new table.

CLI Options

Usage: sync-mcp [options]

Options: --api-key API key (or set SYNC_API_KEY env var) --base-url API base URL (default: https://api.sync.so) --transport stdio (default) or http --port HTTP port (default: 3002, only with --transport http) --no-spend-confirmation Unattended automation: drop the cost-quote and confirm-before-paying instructions (or set SYNC_MCP_SPEND_CONFIRMATION=off) --no-update-check Skip the daily npm check for a newer version (or set SYNC_MCP_UPDATE_CHECK=off; skipped when CI is set) --toolsets stdio only: comma-separated tools to list (or set SYNC_MCP_TOOLSETS): default, lipsync, dubbing, assets, projects, transcription, voices, admin or all (default: the hosted set without admin) -h, --help Show this help message

Unattended automation

By default the tools tell the agent to quote a paid action and wait for the user's approval. When the server runs a pipeline or a scheduled agent whose operator has already approved spending, start it with --no-spend-confirmation (or SYNC_MCP_SPEND_CONFIRMATION=off). The agent then creates jobs without quoting or asking, and estimate tools stay available. Agents cannot change this setting.

Job tools take wait: true to wait on the server (up to about 50 seconds per call, with progress notifications when the client sends a progressToken): generations_get, translation-previews_get, transcriptions_get and social imports through assets_create. On the local server, jobs_wait and jobs_get do the same for every kind of job (generation, transcription, speaker analysis, translation preview, import) with one input, {kind, id, projectId?}, and one result shape and status set; see Jobs.

When the API offers it, feedback_send lets agents report confusing errors, wrong results and missing capabilities to the Sync team.

Environment variables and the HTTP server's session, memory, upload and diagnostics limits are in [HTTP server configuration](d

Only the beginning is shown; read the rest in the repo

sync. labs

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

MCP Server Autocad Lisp Helper

README from the maker

sync. MCP server

Connect your agent

ChatGPT

Claude (claude.ai and Claude Desktop)

Claude Code

Codex

Cursor

VS Code

Other clients

Local server with an API key

Update notice

What to ask

Agent skills

Tools

Local toolsets

CLI Options

Unattended automation