S
synchronicity-labs/mcp-server
Connect your AI agent to sync.
★ 1·updated 2026-11-18
View on GitHub ↗Direct link · no redirect page
We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 1 ★ · synchronicity-labs/mcp-server · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 1 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
synchronicity-labs/mcp-server;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# sync. MCP server
Excerpted from the repository README (abridged)
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)
1. Open Settings → Connectors and choose Add custom connector.
2. Name it sync. and set the URL to https://mcp.sync.so/mcp.
3. Click Connect and sign in to sync.
### Claude Code
bash
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
bash
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:
json
"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:
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:
bash
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:
json
"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.
#### Sign in with an emailed code
A command-line agent can sign you in without a browser and add the server itself.
It runs two commands and you read it one code from your inbox:
bash
npx -y @sync.so/mcp-server@latest setup --email you@example.com
# sync. emails you a code; give it to the agent
npx -y @sync.so/mcp-server@latest setup --code 123456
Or ask your agent: "Set up sync. for me with
npx -y @sync.so/mcp-server@latest setup. My email is you@example.com."
setup adds the server for every project in Claude Code and Codex. Any other
agent is told what to add. login takes the same options and only signs in.
A new email gets a new sync. account. An existing account connects its personal
workspace; connect a team workspace through the hosted server instead. sync. emails
you when an agent connects, with a link that disconnects it. --agent is the name
that email shows. The sign-in is saved in ~/.config/sync/mcp-credentials.json and
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)
1. Open Settings → Connectors and choose Add custom connector.
2. Name it sync. and set the URL to https://mcp.sync.so/mcp.
3. Click Connect and sign in to sync.
### Claude Code
bash
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
bash
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:
json
"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:
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:
bash
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:
json
"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.
#### Sign in with an emailed code
A command-line agent can sign you in without a browser and add the server itself.
It runs two commands and you read it one code from your inbox:
bash
npx -y @sync.so/mcp-server@latest setup --email you@example.com
# sync. emails you a code; give it to the agent
npx -y @sync.so/mcp-server@latest setup --code 123456
Or ask your agent: "Set up sync. for me with
npx -y @sync.so/mcp-server@latest setup. My email is you@example.com."
setup adds the server for every project in Claude Code and Codex. Any other
agent is told what to add. login takes the same options and only signs in.
A new email gets a new sync. account. An existing account connects its personal
workspace; connect a team workspace through the hosted server instead. sync. emails
you when an agent connects, with a link that disconnects it. --agent is the name
that email shows. The sign-in is saved in ~/.config/sync/mcp-credentials.json and
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/synchronicity-labs-mcp-server/)
- Source
- awesome · https://github.com/synchronicity-labs/mcp-server
- Browse by field
- MCP servers
- Traction
- 1 ★
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.