Skip to main content
Glama

Related Servers

Alternatives to seafile-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      MIT
    • 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
    • A
      license
      A
      quality
      B
      maintenance
      Connects 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.
      5
      MIT
    • 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
    • A
      license
      B
      quality
      B
      maintenance
      Connects MCP clients to a self-hosted Harbor registry's official /api/v2.0 REST API, letting them query projects, repositories, artifacts, tags, robots, and system health, and perform confirmation-gated writes such as project, tag, label, and scan operations. Runs over stdio or stateless Streamable HTTP on localhost with Basic auth and secret redaction.
      6
      MIT
    • F
      license
      C
      quality
      D
      maintenance
      Schema-driven MCP server that exposes all Paperclip API operations as typed MCP tools over stdio or Streamable HTTP, supporting both authenticated and local_mode deployments.
      100
      -

    TDQS

    B3.1/5.0

    Scored across 4 tools

    Disambiguation3/5

    The four tools split the surface by domain (files/dirs, libraries, search, server), which gives an agent a rough first cut, but boundaries leak: directory and file operations appear in both seafile_files_and_dirs and seafile_libraries, and each tool is a flat bundle of dozens of raw route actions (delete_dir vs delete_repos_dir, get_repo vs get_repos, list_repos vs list_repos_get, post_repo vs update_repos_*) that are hard to tell apart without reading full path semantics. Within each tool the agent must select among 6–74 near-duplicate REST endpoints, so misselection risk is high even though the four top-level buckets are reasonably distinct.

    Naming Consistency4/5

    Tool names follow a clean, predictable seafile_<domain> pattern (seafile_files_and_dirs, seafile_libraries, seafile_search, seafile_server) in consistent snake_case. However, the internal action names exposed inside each tool swing between clean task verbs (list_dir, delete_file, search_file) and raw route-derived artifacts (copy_repos_fileops, delete_repos_batch_delete_folders_item, post_repos_sync_batch_copy_item), which undermines the usability of the naming for selection.

    Tool Count2/5

    Only four tools carry roughly 165 underlying operations (74 + 39 + 6 + 46), so the surface is massively over-compressed into mega-tools rather than scoped by user intent. The tool count is nominally small but functionally far too coarse, forcing agents to navigate huge enumerated action lists for routine operations.

    Completeness3/5

    Core areas — library CRUD, file/dir operations, comments, locking, batch copy/move, upload/download links, search, account and server admin — are covered, so basic workflows have no dead ends. But major Seafile domains are absent: sharing/permissions, groups, trash/recycle-bin restore, file revisions, activities/notifications, wikis, and sync, despite sharing-related zip-task endpoints being present.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues