Skip to main content
Glama
URBackup MCP
by MarkPhsd

Related Servers

Alternatives to URBackup MCP

No user-submitted related servers found.

    Related Servers

    • 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
      D
      maintenance
      MCP server for administering Duplicacy backups via the duplicacy-web API, enabling AI clients to inspect and manage storages, repositories, schedules, and jobs.
      15
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server enables AI agents to interact with a self-hosted database backup and recovery platform through Streamable HTTP tools, including scoped access to connections, backup schedules, snapshots, jobs, downloads, deletion, and restore operations. It supports review-before-restore workflows and delegated credentials with expiry and revocation.
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A typed MCP server for curated backup administration of DBackup via its API, exposing tools for backup jobs, execution history, notifications, storage, and bounded restore workflows.
      MIT
    • 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
      87 npm
      MIT

    TDQS

    B3.3/5.0

    Scored across 31 tools

    Disambiguation4/5

    Most tools map to a clear resource+action pair (restore_files vs restore_image, archive vs unarchive vs delete, start_backup vs stop_process). The only real collision is urbackup_get_logs (list logs) versus urbackup_get_log (fetch entries of a log), plus a softer overlap between urbackup_status, urbackup_status_check and urbackup_progress, but descriptions make the intent separable.

    Naming Consistency4/5

    All names share the urbackup_ prefix and snake_case, and the dominant pattern is verb_noun (get_general_settings, save_client_settings, create_user, remove_user, delete_backup). The deviations are noun-only names such as urbackup_status, urbackup_progress, urbackup_status_check, urbackup_usage_stats and urbackup_usage_graph, which break the pattern but remain readable.

    Tool Count3/5

    31 tools is on the heavy side, and the surface can feel crowded across settings, users, stats, monitoring and restore paths. However, UrBackup is a full backup-server administration API and nearly every tool covers a distinct administrative operation, so the count is defensible rather than bloated.

    Completeness4/5

    Coverage is strong: backup lifecycle (start/list/archive/unarchive/delete), restore (files, image, browse, downloads), settings (general, client, mail), user CRUD with rights and passwords, logs, process control, and usage stats. Notable gaps are client/group management (no create/remove client, no group-level settings even though group origin is referenced) and no way to remove or edit extra clients.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues