Compatible with every major AI agent and IDE
What is the Syncthing MCP Server?
Connect your Syncthing instance to any AI agent and take full control of your private file synchronization infrastructure through natural conversation.
What you can do
- Device Monitoring — List all configured devices and check their real-time connection status and metadata.
- Folder Management — Query all synchronized folders, check their database status, and monitor completion percentages.
- System Control — Pause or resume synchronization for specific devices, restart the Syncthing process, or check if a configuration change requires a restart.
- Directory Browsing — Remotely list directories matching specific paths to verify file structures across your sync network.
- Configuration & Stats — Fetch or update the entire system configuration and retrieve detailed statistics for folders and devices.
How it works
- Subscribe to this server
- Enter your Syncthing Web UI URL and API Key
- Start managing your P2P sync network from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Sysadmins & DevOps — monitor distributed sync nodes and manage configurations without leaving the terminal or chat interface.
- Power Users — check the health of home lab backups and trigger folder scans or device resumes via voice or text.
- Data Managers — verify that specific files have synced across the network by browsing remote directories through the AI.
Built-in capabilities (28)
Get entire configuration
Get folder/device completion status
Get detailed data about a specific file
Get ignore patterns for a folder
). Get folder database status
Get specific device configuration
Get device statistics
Get all configured devices
Poll for events
Get specific folder configuration
Get folder statistics
Get all configured folders
Returns {"status": "OK"}. Does not require authentication. Simple health check
Get a strong random alphanumeric string
Check if restart is required
Request immediate scan of a folder
Replace entire configuration
Set ignore patterns for a folder
List directories matching a path
Get configured devices and connection status
If device ID is omitted, affects all devices. Pause devices
Optionally reset only a specific folder. Reset index database
Restart Syncthing
If device ID is omitted, affects all devices. Resume devices
Shutdown Syncthing
). Get current system status and resource usage
Get Syncthing version
Verify and format a device ID
Why VS Code Copilot?
GitHub Copilot Agent mode brings Syncthing data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 28 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Syncthing in VS Code Copilot
Syncthing and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Syncthing to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Syncthing in VS Code Copilot
The Syncthing MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 28 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Syncthing for VS Code Copilot
Every tool call from VS Code Copilot to the Syncthing MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can I check if Syncthing needs a restart after I changed the configuration?
You can use the get_restart_required tool. It will return a boolean indicating if a restart is pending due to configuration changes.
Is it possible to pause synchronization for a specific device using the AI?
Yes. Use the system_pause tool and provide the specific Device ID. If you omit the ID, it will pause all devices.
Can I see which files are currently being synchronized?
You can use get_db_status or get_db_completion for a specific folder to see the synchronization progress and state of the files in that directory.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Clerk
6 toolsAdd production-ready authentication to your app with user management, SSO, multi-factor auth, and session handling out of the box.

Smsmobile
26 toolsTurn your smartphone into an SMS/WhatsApp gateway — send messages, read incoming texts, and track call logs directly from any AI agent.

Home River Group
10 toolsConnect and manage Home River Group properties, units, and residents via Entrata API.

ONES
10 toolsEnterprise R&D project management platform — manage tasks, projects, and workflows via AI.
