4,000+ servers built on vurb.ts
Vinkius

Syncthing MCP Server for VS Code CopilotGive VS Code Copilot instant access to 28 tools to Get Config, Get Db Completion, Get Db File, and more

MCP Inspector GDPR Free for Subscribers

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Ask AI about this MCP Server for VS Code Copilot

The Syncthing MCP Server for VS Code Copilot is a standout in the Loved By Devs category — giving your AI agent 28 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Classic Setup·json
{
  "mcpServers": {
    "syncthing": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Syncthing and 4,000+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Syncthing
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About Syncthing MCP Server

Connect your Syncthing instance to any AI agent and take full control of your private file synchronization infrastructure through natural conversation.

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.

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.

The Syncthing MCP Server exposes 28 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 28 Syncthing tools available for VS Code Copilot

When VS Code Copilot connects to Syncthing through Vinkius, your AI agent gets direct access to every tool listed below — spanning file-synchronization, p2p, data-backup, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

get

Get config on Syncthing

Get entire configuration

get

Get db completion on Syncthing

Get folder/device completion status

get

Get db file on Syncthing

Get detailed data about a specific file

get

Get db ignores on Syncthing

Get ignore patterns for a folder

get

Get db status on Syncthing

). Get folder database status

get

Get device on Syncthing

Get specific device configuration

get

Get device stats on Syncthing

Get device statistics

get

Get devices on Syncthing

Get all configured devices

get

Get events on Syncthing

Poll for events

get

Get folder on Syncthing

Get specific folder configuration

get

Get folder stats on Syncthing

Get folder statistics

get

Get folders on Syncthing

Get all configured folders

get

Get health on Syncthing

Returns {"status": "OK"}. Does not require authentication. Simple health check

get

Get random string on Syncthing

Get a strong random alphanumeric string

get

Get restart required on Syncthing

Check if restart is required

scan

Scan db on Syncthing

Request immediate scan of a folder

set

Set config on Syncthing

Replace entire configuration

set

Set db ignores on Syncthing

Set ignore patterns for a folder

system

System browse on Syncthing

List directories matching a path

system

System connections on Syncthing

Get configured devices and connection status

system

System pause on Syncthing

If device ID is omitted, affects all devices. Pause devices

system

System reset on Syncthing

Optionally reset only a specific folder. Reset index database

system

System restart on Syncthing

Restart Syncthing

system

System resume on Syncthing

If device ID is omitted, affects all devices. Resume devices

system

System shutdown on Syncthing

Shutdown Syncthing

system

System status on Syncthing

). Get current system status and resource usage

system

System version on Syncthing

Get Syncthing version

verify

Verify device id on Syncthing

Verify and format a device ID

Connect Syncthing to VS Code Copilot via MCP

Follow these steps to wire Syncthing into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Create MCP config

Create a .vscode/mcp.json file in your project root
02

Add the server config

Paste the JSON configuration above
03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown
04

Start using Syncthing

Ask Copilot: "Using Syncthing, help me...". 28 tools available

Why Use VS Code Copilot with the Syncthing MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Syncthing through the Model Context Protocol.

01

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

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Syncthing + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Syncthing MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Example Prompts for Syncthing in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Syncthing immediately.

01

"Show me all connected devices and their current status."

02

"Check the system status and resource usage of my Syncthing instance."

03

"List the directories inside the path '/data/backups/photos'."

Troubleshooting Syncthing MCP Server with VS Code Copilot

Common issues when connecting Syncthing to VS Code Copilot through Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Syncthing + VS Code Copilot FAQ

Common questions about integrating Syncthing MCP Server with VS Code Copilot.

01

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.
02

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.
03

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.
04

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.

Explore More MCP Servers

View all →