duplicacy-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DUPLICACY_EXPORTER_URL | Yes | Duplicacy Prometheus exporter URL |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_backup_historyC | Get the last backup details for a specific Duplicacy snapshot (files, bytes, duration, exit code) |
| get_backup_statusB | Get the current backup status for a specific Duplicacy snapshot |
| get_prune_statusC | Get the prune operation status, optionally filtered by storage target |
| list_snapshotsB | List all unique Duplicacy snapshot IDs known to the exporter |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Active backup progress | Real-time progress of any running backups (speed, progress %, chunks uploaded/skipped) |
| All backup statuses | Parsed Prometheus metrics showing all backup statuses (running/idle, last success, exit code per snapshot) |
| Exporter health check | Health status of the duplicacy-exporter service |
TDQS
Scored across 4 tools
Tools have clearly distinct purposes, though get_backup_history and get_backup_status both target specific snapshots with similar naming patterns (historical vs current status). The descriptions adequately clarify the distinction between completed backup details and ongoing operations.
All four tools follow a strict verb_noun pattern using snake_case (get_backup_history, get_backup_status, get_prune_status, list_snapshots). The naming convention is uniform and predictable throughout the set.
Four tools is reasonable for a focused observability server interfacing with a Duplicacy exporter, providing essential monitoring capabilities without excessive scope. However, the read-only nature limits the server's overall utility for backup operations.
As a monitoring-specific server, it covers basic backup status, history, and prune operations, but lacks storage metrics, verification/check status, and error log access. For general Duplicacy management, the absence of backup execution, restore, or configuration tools represents notable functional gaps.