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 CrewAI?
When paired with CrewAI, Syncthing becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Syncthing tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Syncthing in CrewAI
Syncthing and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Syncthing to CrewAI 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 CrewAI
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 CrewAI 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 CrewAI
Every tool call from CrewAI 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.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
Sigma Computing
7 toolsEquip your AI agent to audaciously navigate your Sigma data workflows. List core workbooks, map connections, trace dataset lineage, and monitor organization teams directly from your IDE.

Paylocity
10 toolsManage payroll and HR via Paylocity — list employees, track earnings, and audit benefits setup directly from any AI agent.

ThinkingData / 数数科技
8 toolsDominant games and app analytics platform — query events, audit users, and track data via AI.

Huginn (IFTTT Alternative)
13 toolsAutomate workflows with Huginn — manage agents, trigger webhooks, and orchestrate complex scenarios directly from your AI agent.
