Vsync
Sync MCP servers, Skills, Agents & Commands across Claude Code, Cursor, OpenCode, Codex. One config, all tools.
What is Vsync?
Vsync is a Model Context Protocol (MCP) server that allows AI assistants like Claude, Cursor, and VS Code to sync mcp servers, skills, agents & commands across claude code, cursor, opencode, codex. one config, all tools.
Sync MCP servers, Skills, Agents & Commands across Claude Code, Cursor, OpenCode, Codex. One config, all tools.
This server falls under the Developer Tools category on MCPgee, the world's largest MCP server directory with 33,000+ servers.
Features
- Sync MCP servers, Skills, Agents & Commands across Claude Co
Use Cases
Maintainer
Works with
Installation
Manual Installation
npx vsyncConfiguration
Configuration Details
claude_desktop_config.json
Performance
Response Metrics
Resource Usage
How to Set Up and Use Vsync
vsync is a CLI tool that synchronises MCP server configurations, skills, agents, and commands across multiple AI coding tools — Claude Code, Cursor, OpenCode, and Codex — from a single source of truth. Instead of manually duplicating MCP JSON configs in four different places, you define them once and run 'vsync sync' to propagate changes everywhere. It intelligently translates environment variable syntax between tools (${VAR} for Claude Code/Cursor, {env:VAR} for OpenCode) and never expands secrets, making it safe for team-shared config files committed to git.
Prerequisites
- Node.js 18 or later with npm
- At least one supported AI coding tool installed: Claude Code, Cursor, OpenCode, or Codex
- An existing MCP server configuration in one of the supported tools to use as the source
- An MCP client (Claude Desktop, Claude Code, Cursor, etc.) for testing synced configurations
Install vsync globally
Install the @nicepkg/vsync package globally so the vsync command is available anywhere, or run it directly with npx.
npm install -g @nicepkg/vsync
# Or run without installing:
npx @nicepkg/vsync --versionRun interactive setup
Run vsync init to create a .vsync.json configuration file. The interactive prompt will ask which tool is your source and which tools are sync targets.
vsync initReview the generated .vsync.json
The init command creates a .vsync.json file. Edit it to set your source_tool, target_tools array, and which config types (mcp, skills, agents, commands) to sync. Commit this file to share settings with your team.
{
"source_tool": "claude-code",
"target_tools": ["cursor", "opencode"],
"sync_config": {
"skills": true,
"mcp": true,
"agents": false,
"commands": true
},
"use_symlinks_for_skills": false,
"language": "en"
}Preview changes with a dry run
Before applying changes, use --dry-run to see exactly what vsync will add, update, or remove across target tools.
vsync sync --dry-runSync your configurations
Run the sync command to propagate your source tool's MCP servers and skills to all target tools. By default, safe mode is used and nothing is deleted from targets.
# Safe sync (no deletions):
vsync sync
# Strict mirror mode (removes entries not in source):
vsync sync --pruneVsync Examples
Client configuration
vsync is a CLI sync tool, not an MCP server itself. No mcpServers block is needed. Configure it via .vsync.json in your project or user home directory.
# Project-level config (committed to git):
# .vsync.json
{
"source_tool": "claude-code",
"target_tools": ["cursor", "opencode", "codex"],
"sync_config": { "mcp": true, "skills": true }
}
# User-level config (personal, not committed):
# ~/.vsync.json
{
"source_tool": "cursor",
"target_tools": ["claude-code"]
}Prompts to try
vsync is a CLI tool. Here are the common commands you will run during day-to-day use.
- "vsync init" — run interactive setup to create .vsync.json
- "vsync sync --dry-run" — preview what will change without writing anything
- "vsync sync" — propagate source configs to all target tools (safe mode)
- "vsync sync --prune" — strict mirror: removes entries in targets not present in source
- "vsync --version" — confirm the installed versionTroubleshooting Vsync
Environment variables are expanded or secrets are leaked during sync.
vsync never expands environment variables — it preserves the original syntax and translates between formats (${VAR} to {env:VAR}) as needed per target tool. If you see raw secret values in the output, ensure you are using variable references in your source config, not hardcoded values.
Synced config does not appear in the target tool after running vsync sync.
Verify the target tool is listed in target_tools in .vsync.json and that sync_config.mcp is set to true. After syncing, restart the target IDE or MCP client to reload its configuration files. Use --dry-run first to confirm vsync can locate the target config paths on your system.
Frequently Asked Questions about Vsync
What is Vsync?
Vsync is a Model Context Protocol (MCP) server that sync mcp servers, skills, agents & commands across claude code, cursor, opencode, codex. one config, all tools. It connects AI assistants to external tools and data sources through a standardized interface.
How do I install Vsync?
Follow the installation instructions on the Vsync GitHub repository. Clone the repo, install dependencies, and add the server config to your AI client.
Which AI clients work with Vsync?
Vsync works with all major MCP-compatible AI clients including Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and Cline.
Is Vsync free to use?
Yes, Vsync is open source and available under the MIT license. You can use it freely in both personal and commercial projects.
Vsync Alternatives — Similar Developer Tools Servers
Looking for alternatives to Vsync? Here are other popular developer tools servers you can use with Claude, Cursor, and VS Code.
Ecc
★ 188.2kThe agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Javaguide
★ 155.8kJava 面试 & 后端通用面试指南，覆盖计算机基础、数据库、分布式、高并发、系统设计与 AI 应用开发
Gemini CLI
★ 104.5kA secure MCP server that wraps the Google Gemini CLI, allowing clients to query Gemini models using local OAuth sessions without requiring an API key. It provides tools for model interaction and diagnostics with built-in protection against command in
Awesome MCP Servers
★ 87.3k⭐ Curated list of Model Context Protocol (MCP) servers - tools that extend Claude Desktop, Cursor, Windsurf, and other MCP clients with custom capabilities.
MCP Servers
★ 86.0kModel Context Protocol Servers
CC Switch
★ 77.5kA cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Gemini CLI & Hermes Agent. Only official website: ccswitch.io
Browse More Developer Tools MCP Servers
Explore all developer tools servers available in the MCPgee directory. Each server includes setup guides for Claude, Cursor, and VS Code.
Set Up Vsync in Your Editor
Choose your AI client for step-by-step setup instructions.
Quick Config Preview
Add this to your claude_desktop_config.json or .cursor/mcp.json
Ready to use Vsync?
Browse our complete directory of 33,000+ MCP servers, read setup guides for your editor, and start building with the Model Context Protocol.