duplicacy-mcp
Related Servers
Alternatives to duplicacy-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for managing Duplicati backups from an LLM.17MIT
- AlicenseBqualityAmaintenanceMCP server that reads Duplicacy backup metrics from a Prometheus exporter and exposes them to LLMs for monitoring backup status, progress, and health.441 npm2GPL 3.0
- AlicenseBqualityDmaintenanceMCP server for Duplicati backup management. Enables checking status, running backups, viewing logs, and controlling the scheduler.21MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for Tidy, a backup and sync app. Enables AI agents to manage folder backups, schedules, and git sync operations via natural language.MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to manage restic backups, including listing snapshots, browsing files, and creating new backups. It provides tools for repository maintenance, data restoration, and applying retention policies through the Model Context Protocol.1-
- FlicenseNot gradedqualityBmaintenanceMCP server for AI DevTool workflow, exposing tools and resources for code review, repository chat, and repository operations.1-
TDQS
Scored across 15 tools
Each tool targets a distinct resource (storage, repository, schedule, job) and a unique action (create, delete, get, set, list). The two status tools are clearly separated by their focus: schedule status vs backup status.
All tool names follow a consistent verb_noun pattern in lower_snake_case (e.g., create_storage, get_filters, delete_job). Verbs are specific and predictable, making the naming uniform and easy to anticipate.
15 tools is well-scoped for a backup management server, covering the core resources without unnecessary bloat. Each tool has a clear role in the lifecycle of storages, repositories, schedules, and jobs.
The tool set provides comprehensive CRUD-like coverage for storages and repositories, full schedule and job lifecycle management, plus filter configuration and status monitoring. No critical operations are missing; any workaround is only for convenience, not necessity.