mcp-sync

Synchronize MCP binary files across .build, mcpb/server, and ~/bin directories.

Updated Jan 10, 2026
One-click install
npx skills add https://github.com/PsychQuant/psychquant-claude-plugins --skill mcp-sync-psychquant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-sync
Source: https://github.com/PsychQuant/psychquant-claude-plugins/tree/main/plugins/mcp-tools/skills/mcp-sync
Command: npx skills add https://github.com/PsychQuant/psychquant-claude-plugins --skill mcp-sync-psychquant

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires swift, lipo, codesign, shasum, file, zip, unzip, grep, sed, chmod, cp, rm, ls, mkdir, cat, and includes scripts (resource) components.

What problem does it solve?

Ensures that the MCP binary files are consistent across your development environment, preventing potential runtime errors due to outdated or mismatched versions.

Core Features & Use Cases

  • Binary Consistency Check: Verifies that binaries in .build, mcpb/server, and ~/bin are identical.
  • Automated Synchronization: Rebuilds, signs, and copies binaries to maintain uniformity.
  • Use Case: After compiling a Swift project, this Skill can ensure the executable is correctly placed and signed in your system's binary path, ready for execution.

Quick Start

Run the mcp-sync skill to check for binary inconsistencies.

Frequently Asked Questions about mcp-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync MCP binaries across multiple Swift project directories?

Syncing MCP binaries involves checking consistency across .build, mcpb/server, and ~/bin directories, then optionally rebuilding, re-signing, and copying files to ensure uniformity.

Why do mismatched MCP binaries cause runtime errors in Swift projects?

Mismatched MCP binaries cause runtime errors when outdated versions exist across locations; consistency checks using hashing and file information prevent these issues by maintaining uniformity.

What is the best way to ensure code signing is consistent for universal Swift binaries?

Ensuring code signing consistency for universal Swift binaries requires re-signing and copying files across .build, mcpb/server, and ~/bin directories to maintain uniformity and prevent errors.

Does this binary synchronization process handle both universal and single-architecture executables?

Yes, the binary synchronization process handles both universal and single-architecture executables, performing consistency checks and re-packaging .mcpb files as needed.

How do I re-package .mcpb files after rebuilding a Swift project?

To re-package .mcpb files after rebuilding, the skill synchronizes the updated binaries, performs consistency checks using hashing, and re-packages the files across your system.

Do I need lipo and codesign to verify binary consistency across my system?

Yes, you need lipo and codesign along with shasum and file to verify binary consistency, as these dependencies are required for checking, signing, and copying binaries.