backrest-mcp
Related Servers
Alternatives to backrest-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceThis 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.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables unified access to multiple MCP backend servers through one local daemon, with curated per-client tool profiles, allow/deny policies, audit logging, and drift protection.46 npm1MIT
- 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.2-
- AlicenseNot gradedqualityBmaintenanceA 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
- AlicenseNot gradedqualityDmaintenanceEnterprise-grade MCP server for Kubernetes operations, supporting local kubeconfig and AWS EKS authentication, with read, write, and destructive operations protected by multi-layer safety guards.MIT

Keepit MCPofficial
AlicenseNot gradedqualityBmaintenanceMCP server for interacting with Keepit backup and data protection services. Enables monitoring, management, and security operations through natural language.5MIT
TDQS
Scored across 11 tools
Each tool targets a distinct resource or question (health, dashboard stats, config, plans, snapshots, files, operations, logs, freshness, download URLs), and descriptions actively steer between near-duplicates like get_config vs list_plans. The main soft overlap is between get_summary, get_backup_freshness, and get_operations, which all touch backup recency/success and could be confused by an agent skimming names.
All tools follow a strict snake_case verb_noun pattern using a small, predictable verb set (get_, list_, find_). No camelCase mixing or vague one-word names.
11 tools is well within the ideal range and each covers a distinct inspection need within a backup orchestrator. No obviously redundant or filler tools; the surface is scoped to read/inspect operations.
The read-only inspection surface is decent (health, config, plans, snapshots, files, operations, logs, freshness), but there are no action tools: no trigger backup, restore, plan/repo create-update, or prune/check/forget. get_download_url explicitly describes itself as a companion to restore_snapshot, a tool that does not exist here, creating a dead end for that workflow.