Skip to main content
Glama
Sign In
Syncthing MCP

Syncthing MCP

by si-essence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Syncthing MCP

No user-submitted related servers found.

    Related Servers

    • Syncthing MCP

      sharkusmanch
      A
      license
      D
      quality
      C
      maintenance
      Enables secure, configurable access to one or more Syncthing instances over MCP, with read-only defaults and opt-in write, destructive, and administrative operations. Supports stdio and authenticated Streamable HTTP transports, typed tools, bounded responses, and multi-instance configuration.
      40
      MIT

    • immich-mcp

      si-essence
      A
      license
      A
      quality
      C
      maintenance
      Connects 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.
      5
      76 npm
      MIT

    • seafile-mcp

      si-essence
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects 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.
      7 npm
      MIT

    • solidtime-mcp

      si-essence
      A
      license
      C
      quality
      C
      maintenance
      Enables MCP clients to manage time entries, projects, tasks, clients, tags, reports, invoices, and related resources through a Solidtime instance's public REST API. Supports stdio and localhost Streamable HTTP with a bring-your-own API token and optional write gating.
      53
      MIT

    • komga

      si-essence
      A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      7
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 5 tools

    Disambiguation4/5

    The five tools are cleanly partitioned by resource domain (system, config, folders, devices, db), so an agent can usually pick the right one from the noun alone. There is some residual overlap: syncthing_system exposes status/errors while syncthing_db exposes folder status/errors/completion, and syncthing_folders.get vs syncthing_db.folder_stats could be confused without reading the action lists.

    Naming Consistency4/5

    All tools share the syncthing_ prefix plus a single domain noun, which is predictable and readable. The names are noun-only rather than verb_noun, and syncthing_db breaks the 'config resource' pattern slightly, so the verb is hidden inside the action parameter.

    Tool Count5/5

    Five tools for a Syncthing admin surface is well-scoped: each domain (system, config, folders, devices, db) earns its place and nothing looks redundant. The heavy action multiplexing is handled inside each tool rather than by inflating the tool count.

    Completeness4/5

    Coverage is strong: read/write lifecycle for folders and devices, config read/patch, pending offers/requests, and runtime status, need, completion, and scan. Minor gaps exist for event/log streaming and version upgrade operations, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources