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 Cursor?
Cursor's Agent mode turns Syncthing into an in-editor superpower. Ask Cursor to generate code using live data from Syncthing and it fetches, processes, and writes. all in a single agentic loop. 28 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Syncthing in Cursor
Syncthing and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Syncthing to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Lusha
6 toolsEquip your AI agent with direct access to Lusha — find verified B2B contact details, enrich prospect data, and build lead lists without opening the Lusha platform.

Lacework (Cloud Security & CNAPP)
10 toolsSecure your cloud via Lacework — search security alerts, monitor vulnerabilities, and audit cloud asset inventory.

Vercel Alternative
14 toolsManage Vercel deployments, projects and domains via API — inspect builds, track deployments, manage env vars and domains from any AI agent.

Marketplacer (Enterprise Marketplace Platform)
9 toolsManage your enterprise marketplace via Marketplacer — list products, track orders, and audit seller networks.
