vsync

vsync is an MCP server integration that centralizes management of Skills, MCP servers, Agents, and Commands across multiple AI tools. It provides a single source-of-truth configuration for your AI coding environment and offers a synchronization workflow to propagate changes safely to all supported targets. With vsync you can treat MCP server configurations as part of a unified configuration system, ensuring consistency across tools like Claude Code, Cursor, OpenCode, Codex, and more. The tool handles format conversion, safe diffs, and atomic writes, so you can preview changes before applying and avoid accidental deletions.

To use vsync, install or run the tool and initialize a project configuration by selecting your source of truth (the primary tool whose settings you want to mirror) and the target tools you want to sync to. After initialization, you can run vsync sync to synchronize Skills, MCP servers, Agents, and Commands across all chosen tools. The workflow includes a diff/plan step so you can review what will change, and supports safe mode (no deletions) as well as prune mode for strict mirroring. The MCP capabilities include managing and syncing MCP servers along with other components, all while preserving environment variable formats during cross-tool migrations.

Prerequisites:

• Node.js and npm installed on your system
• Access to the internet to fetch the npm package

Option A: Run directly with npx (no installation required)

1. Ensure you have Node.js installed
2. Run: npx @nicepkg/vsync

Option B: Install globally with npm

1. Ensure you have Node.js and npm installed
2. Install the package globally: npm install -g @nicepkg/vsync
3. Verify installation: vsync --version

Option C: Install as a local project dependency

1. In your project folder, run: npm init -y npm install @nicepkg/vsync --save-dev
2. Run via npx within the project context or set up an npm script in package.json: npx vsync

Notes:

• The tool supports both safe mode (default) and prune mode for strict mirroring. Use --prune to enable deletions.
• You can initialize both project-level (repo-wide) and user-level configurations as needed.

Tips and common issues:

• Ensure your source tool is reachable and selected correctly during vsync init to avoid misconfiguration.
• If environment variables need to be preserved across tools, rely on vsync's cross-format conversion features; avoid manual edits that may break compatibility.
• Use the dry-run option (vsync sync --dry-run) to preview changes before applying them.
• For large configurations, the tool performs parallel operations and uses atomic writes to minimize partial updates.
• If you encounter path or permission issues during writes, run with appropriate permissions or adjust the target directories in your environment.