
opencode-sync-mcp-server
Updated todayby severin-ye
opencode-sync
One command to backup. One command to restore. Your entire dev environment, synced across machines.
Export your opencode workspace — submodules, configs, skills, API keys — to a private GitHub repo.
On a new machine, pull it back and everything installs itself.
Why?
You have multiple machines. Each has opencode with different plugins, MCP servers, skills, and submodules checked out at different commits. Keeping them in sync is a nightmare of git submodule update, npx skills add, and copy-pasting config files.
opencode-sync makes it a single command:
# On your main machine
opencode_sync_push "Friday backup"
# On your new laptop
opencode_sync_pull
That's it. Submodules reset to exact commits. MCP servers rebuilt. Skills reinstalled. Config merged. API keys templated. Everything just works.
Quick Start
# 1. Install
git clone https://github.com/<you>/opencode-sync-mcp-server
cd opencode-sync-mcp-server
npm install && npm run build
# 2. Add to your opencode config (~/.config/opencode/opencode.jsonc)
# {
# "mcp": {
# "opencode-sync": {
# "type": "local",
# "command": ["node", "<path-to>/dist/index.js"],
# "enabled": true
# }
# }
# }
# 3. Restart opencode, then:
opencode_sync_init # detect your workspace
opencode_sync_push "init" # first backup
New machine?
opencode_sync_init initType=sync githubUrl=<url>thenopencode_sync_pull.
What It Syncs
| Category | What | How |
|---|---|---|
| Submodules | All 14+ repos, exact commit hash | git clone + git reset --hard |
| OpenCode Config | plugins, MCP servers, providers | Deep-merge, never overwrite |
| Skills | 40+ installed skills | npx skills add <source> -g from known source map |
| API Keys | Names + descriptions (never values) | Template file at keys/API.md |
| Dependencies | gh CLI, Ralph, Skills CLI | Auto-install via winget/brew/apt/npm |
| Windows Fixes | NTFS path issues | Auto-detects problematic filenames, applies git config core.protectNTFS |
| Install Log | Every install, its source, any pitfalls | state/install-log.json — provenance you can trust |
Tools (13)
| Tool | What it does |
|---|---|
opencode_sync_init | Detect workspace, guide first-time setup. Only asks once. |
opencode_sync_push | Export state → commit → push to GitHub. One command. |
opencode_sync_pull | Pull from GitHub → restore everything. One command. |
opencode_sync_export | Export full workspace state as JSON |
opencode_sync_import | Restore from JSON (with dryRun preview) |
opencode_sync_diff | Compare current state vs saved state |
opencode_sync_status | Show every submodule: commit, branch, dirty? |
opencode_sync_verify | Health check: gh, git, config, ralph, skills, submodules |
opencode_sync_setup | Install everything: gh, submodules, config, ralph, skills CLI, skill packages |
opencode_sync_create_repo | Create a private GitHub repo (warns if public) |
opencode_sync_api_keys | Detect, template, or add API keys |
opencode_sync_guide | Generate guide/SYNC-GUIDE.md — the restore playbook |
opencode_sync_log | Read/write install provenance log |
Architecture
Related servers

n8n
Updated todayby n8n-io
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.

mcp-server-fetch
OfficialUpdated 14d agoA Model Context Protocol server providing tools to fetch and convert web content for usage by LLMs

@modelcontextprotocol/server-everything
OfficialUpdated 14d agoMCP server that exercises all the features of the MCP protocol