Theme

Download and install the MCP adapter ​

ss-mcp is one executable with no installer, no service and no configuration file. You download the archive for the machine your AI agent runs on, verify it, put the executable where you want it, and point the agent at it. This article covers the first three steps; the agent side is in Connect your AI agent.

Where to download it ​

The adapter is on the Syncplify download page, under Syncplify Server!. The current release is always at these direct addresses:

Your machineDownloadInside
Linux, 64 bit Intel or AMDss-mcp-linux-x64.tar.gzss-mcp, README.txt
Linux, 64 bit ARMss-mcp-linux-arm64.tar.gzss-mcp, README.txt
Windows, 64 bitss-mcp-win-x64.zipss-mcp.exe, README.txt
Checksumsss-mcp-SHA256SUMS.txtone SHA256 line per archive

Versioned copies, such as ss-mcp-1.0.0-linux-x64.tar.gz with its own ss-mcp-1.0.0-SHA256SUMS.txt, sit next to the current ones for installations that pin a version.

Where should it run?

On the machine that runs the agent: the laptop with Claude Desktop, the workstation with Claude Code or your IDE, or a Linux machine the agent reaches over SSH. It does not have to run on the Syncplify Server! machine, and it is better that it does not. There is no macOS build; a Mac uses an adapter installed on a Linux machine over SSH, as shown in Connect your AI agent.

Linux ​

The six commands below download the archive and the checksum file, verify the archive, extract it, install the executable and print its version:

bash
curl -fsSLO https://dl.syncplify.com/ss-mcp-linux-x64.tar.gz
curl -fsSLO https://dl.syncplify.com/ss-mcp-SHA256SUMS.txt
sha256sum --check --ignore-missing ss-mcp-SHA256SUMS.txt
tar -xzf ss-mcp-linux-x64.tar.gz
sudo install -m 0755 ss-mcp /usr/local/bin/ss-mcp
ss-mcp --version

On an ARM machine use ss-mcp-linux-arm64.tar.gz in the first and fourth command. The checksum line must print ss-mcp-linux-x64.tar.gz: OK; the last command prints something like ss-mcp 1.0.0 (built 2026-11-20T09:12:44Z, commit 3f9c1a2).

Windows ​

  1. Download ss-mcp-win-x64.zip and ss-mcp-SHA256SUMS.txt into the same folder.

  2. Verify the archive. In PowerShell, in that folder:

    powershell
    Get-FileHash .\ss-mcp-win-x64.zip -Algorithm SHA256
Select-String ss-mcp-win-x64.zip .\ss-mcp-SHA256SUMS.txt

    The two hash values must be identical.

  3. Extract the archive into a folder of its own, for example C:\Program Files\ss-mcp (Windows asks for administrator approval for that folder; %LOCALAPPDATA%\Programs\ss-mcp needs none).

  4. Right click ss-mcp.exe, Properties, Digital Signatures: the signer is Syncplify, Inc.

  5. Check that it runs:

    powershell
    & "C:\Program Files\ss-mcp\ss-mcp.exe" --version

You do not need to add the folder to the PATH: every MCP client is given the full path of the executable.

If an antivirus or SmartScreen holds the file back

Verify the checksum and the Authenticode signature as above before you allow it. A file that fails either check is not ours; download it again from the addresses on this page.

Updating ​

Replace the executable with the one from a newer archive while no agent is running it. The adapter keeps nothing anywhere else, so there is nothing to migrate. The adapter and the server do not have to be updated at the same time: an older adapter simply does not offer what a newer server added, and a newer adapter leaves out, when it starts, the tools an older server does not have.

Next ​

Connect your AI agent: create the automation token and configure the client.