Syncthing MCP
Related Servers
Alternatives to Syncthing MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceConnects MCP clients to a self-hosted Syncthing instance's GUI REST API for reading configuration, folders, devices, and connections, plus gated write actions like adding or patching folders and devices, scanning, pausing, restarting, and shutting down. Supports stdio and localhost-only Streamable HTTP with API-key auth, dry-run write previews, redaction of secrets, caching, and rate limiting.5MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to interact with a self-hosted comic/library server through its HTTP API, exposing libraries, series, books, collections, readlists, metadata, and administrative operations with read/write safety controls over stdio or Streamable HTTP.7MIT
- AlicenseBqualityBmaintenanceConnects MCP clients to a self-hosted Seafile server through the seahub HTTP API, exposing libraries, files, search, sharing, and optional admin operations over stdio or Streamable HTTP. It defaults to read-focused tools and gates writes behind confirmation, with token redaction and dry-run previews.4MIT
- AlicenseBqualityBmaintenanceEnables MCP clients to manage a self-hosted backup server through its web API — checking status, starting and stopping backups, browsing and restoring files or disk images, archiving and deleting backups, and reading logs, settings, users, and usage statistics. Destructive operations require explicit confirmation, and it runs over stdio or a Bearer-authenticated streamable HTTP transport.31GPL 3.0
- AlicenseAqualityCmaintenanceConnects MCP clients to a self-hosted photo library through its REST API, exposing assets, albums, people, search, and optional administrative toolsets with read-only defaults and confirm-gated writes. It supports stdio and localhost Streamable HTTP transports.5MIT
- AlicenseCqualityBmaintenanceEnables MCP clients to inspect and manage Semaphore UI automation through its management API, covering projects, templates, tasks, logs, inventories, repositories, and related configuration. It works over stdio or Streamable HTTP with schema-validated tools, read-only mode, project allowlists, and a bounded task-wait helper.213MIT
TDQS
Scored across 40 tools
Many tools are terse nouns with overlapping scopes: config vs options, devices vs device_config/defaults/statistics, folder_status vs folder_completion/statistics/errors. An agent cannot reliably tell which tool to call for a given Syncthing operation without more description.
All tools consistently use snake_case with the syncthing_ prefix, which is predictable and readable. However, they are mostly noun phrases rather than verb_noun action patterns, so the convention is consistent but not action-oriented.
40 tools is excessive for a single MCP server, especially with many terse and overlapping endpoints. Although Syncthing has a broad API, this surface is heavy and difficult to navigate.
The tools cover many read/status/config areas such as devices, folders, events, connections, and statistics, but key lifecycle operations like adding/removing folders or devices, scanning, pausing, or resuming are not clearly represented. Some CRUD coverage may exist through config tools, but it is not evident from the surface.