Syncthing MCP. Manage P2P File Syncs with Conversation.
Syncthing. Take full, conversational control over your private file synchronization networks. This MCP lets you monitor every connected device, check folder completion status across remote nodes, and manage the sync process—all without touching a terminal window. You can verify directory structures remotely or pause specific devices instantly, making it ideal for system admins managing distributed data backups.
Give Claude and any AI agent real-world access
See which devices are connected, their current status, and overall connection metadata.
Pause or resume syncing for specific nodes, or restart the entire Syncthing process when needed.
Determine if a folder has completed synchronization and retrieve detailed status reports on database health.
Remotely list directories matching specific paths across your entire sync network for auditing or verification.
Retrieve the full system configuration, check if a restart is required, or even shutdown the service.
Ask an AI about this
Waiting for input…
What AI agents can do with Syncthing: 25 Tools for File Sync Operations
These tools allow you to perform every operational task on your syncthing instance—from checking connection status and listing directories to pausing services or resetting databases.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Syncthing MCPSystem Browse
Lists directories based on a provided file path.
System Connections
Retrieves all configured devices and their active connection status.
Get Db Completion
Provides the current synchronization completion percentage for a folder or device.
Get Db File
Retrieves detailed metadata and status information about one specific file.
Scan Db
Triggers an immediate synchronization scan request for a specified folder.
Get Db Status
Checks the overall database status of a synchronized folder.
Get Device Stats
Gets detailed performance and resource statistics for a connected device.
Get Events
Polls the system to check for recent synchronization or connection events.
Get Folder Stats
Retrieves comprehensive statistics and usage data for a specific synchronized folder.
Get Config
Fetches the complete, current system configuration settings.
Get Db Ignores
Retrieves the list of ignore patterns set for a specific folder's database.
Get Device
Fetches the detailed configuration settings for one specified device ID.
Get Devices
Retrieves a list of all configured devices and their current connection details.
Get Folder
Fetches the detailed configuration settings for one specified folder path.
Get Folders
Retrieves a list of all configured folders and their respective paths.
Get Health
Performs a simple, non-authenticated check to confirm the overall operational status...
System Pause
Temporarily halts synchronization activity on specified devices or all devices if no...
Get Random String
Generates a strong, random alphanumeric string for use in configuration files.
System Reset
Resets the index database for one or more specified folders.
Get Restart Required
Checks if a system configuration change mandates a full service restart.
System Restart
Initiates a controlled restart of the entire Syncthing service instance.
System Resume
Resumes synchronization activity on specified devices or all devices if no ID is...
Set Config
Replaces the entire system configuration with a new set of parameters.
Set Db Ignores
Sets or updates the ignore patterns for a specified folder's database.
System Shutdown
Gracefully shuts down the Syncthing service instance.
System Status
Gets the current system status and resource usage metrics of the running process.
Verify Device Id
Validates and formats a raw device ID string into the required operational format.
System Version
Retrieves the current software version number of the Syncthing instance.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Syncthing, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Syncthing. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Checking on Your Backup Network Is a Nightmare of Dashboards
Today, checking your multi-node backup network means jumping between multiple web UIs. You check the main dashboard for device status, then open another tab to see folder completion percentages, and finally, maybe you have to run a separate command just to list directories to verify file paths. It's tedious copy-pasting and switching context.
With this MCP, you talk directly to your agent. You ask it, 'What's the status of the Q4 backup?' The agent pulls in device health via `get_devices`, checks folder completion using `get_db_completion`, and verifies file paths—all in one response. You get actionable data without leaving your chat window.
Syncthing MCP Gives You Complete System Control
Manual control used to require knowing which specific CLI command to run, and often required a restart just to make simple changes. If you needed to pause one device while the others kept running, it was complicated.
Now, if you tell your agent to `system_pause` a specific ID, that happens immediately. You manage the network like an operating system—directing power, checking resource usage with `system_status`, and getting immediate confirmation of what changed.
What Syncthing MCP does for your AI
Managing peer-to-peer file synchronization used to mean running multiple command-line tools just to get an overview of what was happening across your network. Now, you connect this MCP and talk to your agent about your infrastructure like natural conversation. You tell it, 'What's the status of my backups?' and it handles the complexity of checking connection health, folder completeness, and device stats.
It gives you a single pane of glass view of your entire sync setup.
Whether you need to pause syncing on one machine because of an outage or browse a specific directory path across multiple nodes just to verify file integrity, your agent can execute those commands. This capability moves deep system control out of the terminal and into chat. By connecting this MCP via Vinkius, you get reliable access to manage complex data flows from any compatible AI client.
It's about gaining visibility and granular control over a distributed network—the kind of operational oversight that used to require specialized knowledge and dozens of manual checks.
019e38f6-e0db-73d3-bb98-768e384c5f2f How to set up Syncthing MCP
The bottom line is you get deep system control over complex file synchronization operations using plain language prompts.
Subscribe to this MCP and provide your Syncthing Web UI URL along with the necessary API key.
Authorize your AI client to interact with your private P2P sync network data.
Ask your agent a question, such as 'Check the status of the marketing folder' or 'Pause syncing on the main backup device', and it executes the required action.
Who uses Syncthing MCP
This MCP is for infrastructure people who manage critical, multi-node data backups. It targets the sysadmin who dreads manually checking multiple command-line outputs or the power user needing granular control over their home lab setup.
Uses this to monitor distributed sync nodes and validate configurations without ever leaving their primary chat interface.
Checks the health of critical backup services, manages connections, and triggers scans across large-scale multi-device deployments.
Verifies that specific files have synced correctly or checks directory paths on remote machines to confirm data integrity before a major migration.
Benefits of connecting Syncthing MCP
You instantly gain visibility into the entire sync network. Instead of checking multiple dashboards, you ask for device status and get a consolidated report on connection health via system_connections.
Avoid manual restarts or complex configuration changes. You can ask your agent to run get_restart_required first, ensuring you only restart the service when absolutely necessary, saving time and preventing downtime.
Confirm data integrity with minimal effort. By asking your agent to list directories using system_browse, you verify file structures across remote nodes without needing SSH into each one.
Maintain control over resource usage by pausing or resuming syncs on specific nodes. You can use system_pause if a device is experiencing high load, and resume it when the issue clears.
Get deep operational stats instantly. Tools like get_folder_stats give you comprehensive reports on folder utilization and completion status faster than any manual check.
Syncthing MCP use cases
Verifying a Critical Backup Path
The data manager needs to confirm that the 'Q4-financial' directory synced correctly across three different NAS units. They ask their agent to use system_browse on specific paths and then run get_folder_stats. The agent replies with confirmation of the file count, eliminating manual checks.
Troubleshooting a Frozen Sync
The ops engineer notices one device is stuck. Instead of guessing, they ask their agent to check both get_device_stats and get_events. The combined data points immediately to a resource bottleneck on the node, allowing them to use system_pause until it's fixed.
Pre-Migration Data Audit
A power user needs an inventory of all sync locations before moving data. They instruct their agent to run get_folders and then use the resulting list to check the configuration for each one using get_folder, building a master checklist in minutes.
Post-Change System Verification
After updating firewall rules, the sysadmin needs to confirm everything is okay. They first use system_status and then ask their agent to check device health via get_health. If both pass, they know the network is operational.
Syncthing MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Assuming Sync Status
Relying on a visual indicator or a basic list to confirm that files have actually reached their target folder.
Always ask your agent to use get_db_completion and get_folder_stats. These tools provide concrete percentage metrics, confirming whether the sync process has truly finished.
Over-relying on Single Commands
Running only system_connections and thinking all systems are green. You miss critical details like current usage or recent errors.
Combine tool calls. Start with get_devices, then follow up by asking the agent to run get_device_stats for any device flagged as 'degraded' for a full picture.
Ignoring Configuration Drift
Assuming your network configuration is correct after an update and not checking what actually changed.
Use get_config to retrieve the current, authoritative system parameters. If you suspect a change, always run this before applying new settings.
When to use Syncthing MCP
Use this MCP if your primary pain point is gaining conversational control and visibility over complex, distributed file synchronization networks (P2P sync). You need to know the health status of multiple nodes, manage resource consumption by pausing services, or remotely audit directory structures. Don't use it if you just need simple cloud storage backups; those are handled by dedicated backup tools that don't require deep system control like this. If your goal is only file retrieval without monitoring sync state, a standard API connector might suffice. But if the process of syncing and the state of the nodes matter, Syncthing is what you need.
Frequently asked questions about Syncthing MCP
How do I check if my Syncthing setup needs a restart using the Syncthing MCP? +
You use the get_restart_required tool. It checks your current configuration against the running service parameters and tells you definitively if a full system restart is necessary before making changes.
Can I list remote files using the Syncthing MCP? +
Yes, use system_browse. You provide the path, and the tool lists matching directories across your entire connected sync network, helping you audit file structures remotely.
What is the difference between `get_folder` and `get_folders` in the Syncthing MCP? +
get_devices retrieves a list of all configured devices. In contrast, get_folders lists every synchronized folder path, while get_folder gets the deep configuration for just one specific path.
How do I check if my backup is finished using Syncthing MCP? +
Use get_db_completion. This tool gives you a quantifiable status, reporting the percentage completion and ensuring the folder has fully synced across all connected nodes.
If I change settings, should I use `set_config` or manually restart? +
Before changing anything, always run get_restart_required. If it indicates a change is needed, you then use the appropriate setter tool (like set_config) followed by system_restart.