Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Lipsync videos, dub them into other languages, make talking videos and open sync. Studio.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
SYNC_API_KEY, SYNC_MCP_TOOLSETS标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mcp.sync.so/mcp打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 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"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http synchronicity-labs https://mcp.sync.so/mcpclaude mcp add synchronicity-labs --env SYNC_API_KEY=your-value --env SYNC_MCP_TOOLSETS=your-value -- npx -y @sync.so/mcp-server运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"synchronicity-labs": {
"url": "https://mcp.sync.so/mcp"
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.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"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"synchronicity-labs": {
"type": "http",
"url": "https://mcp.sync.so/mcp"
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"synchronicity-labs": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@sync.so/mcp-server"
],
"env": {
"SYNC_API_KEY": "your-value",
"SYNC_MCP_TOOLSETS": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mcp.sync.so/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
SYNC_MCP_TOOLSETS env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 synchronicity-labs 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 84 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:SYNC_API_KEY
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(0.2.4)于今天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Master CSS
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Inspect Master CSS classes, generated CSS, and project stylesheets from your AI client.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
Open sync. in ChatGPT and connect your account. In ChatGPT, sync. Studio also opens inside the chat.
sync. and set the URL to https://mcp.sync.so/mcp.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 mcp add sync --url https://mcp.sync.so/mcp
codex mcp login sync
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.
Add to .vscode/mcp.json:
{
"servers": { "sync": { "type": "http", "url": "https://mcp.sync.so/mcp" } } }
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.
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.
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.
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.
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.
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.
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.
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
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
只显示了开头部分;其余内容请在仓库中阅读