mcp -updater

MCP Server Updater is a PowerShell-based tool designed to analyze Claude Desktop's MCP servers, detect their Git repositories, determine the appropriate build and update commands for each server, and safely apply updates with optional backups. It reads your Claude Desktop configuration, locates each MCP server on disk (including parent directories if needed), and identifies the correct project type (Node.js, Python, Go, Java, Rust, .NET, C/C++) to run the appropriate install and build steps after updating. The updater then optionally stashes uncommitted changes, pulls the latest code, installs dependencies, and builds the project using the detected toolchain. You’ll receive a detailed report and can confirm which servers to update before any changes are applied.

Prerequisites:

• Windows 10/11 with PowerShell 5.1 or later
• Git installed and available in PATH
• Claude Desktop installed
• Access to the MCP servers you want to manage via Claude Desktop

Installation steps:

1. Install Git (if not already installed) and ensure it's in your system PATH.
2. Clone the MCP Server Updater repository: git clone https://github.com/JayceeB1/mcp-server-updater.git cd mcp-server-updater
3. Ensure the updater script is executable in PowerShell (optional): Set-ExecutionPolicy RemoteSigned -Scope CurrentUser
4. Run the updater (from PowerShell): .\Update-MCP-Servers.ps1

Optional: specify a language for localization if supported by your environment: .\Update-MCP-Servers.ps1 -Language fr-FR

Notes:

• The updater reads configuration from %APPDATA%\Claude\claude_desktop_config.json, so Claude Desktop should be installed and configured prior to use.

Tips and notes:

• The tool automatically detects the Git repositories for each MCP server, including parent directories if the repository isn’t located in the immediate server directory.
• Before applying updates, the updater creates backups of uncommitted changes (via git stash) if such changes exist.
• The update flow installs dependencies, builds the updated code, and reports success or failure per server. Ensure your environment has the necessary build tools for each project type (e.g., npm, pip, mvn, go, dotnet, etc.).
• You can customize the backup location and log verbosity via MCP_UPDATER_BACKUP_DIR and MCP_UPDATER_LOG_LEVEL environment variables.
• If you encounter issues with localization, ensure strings files exist under Strings/<locale> as described in the project documentation.
• This tool is cross-technology aware and will select the correct commands for each detected project type.