
Duplicati Mcp
io.github.kcofoniPublished by GitHub account kcofoniv1.1.1Updated Oct 25, 2026
MCP server for Duplicati backup management — list, run, monitor and configure jobs from an LLM.
Overview
MCP server that lets an assistant list, run, monitor and configure Duplicati backup jobs through the Duplicati REST API.
- What you can do
- List and inspect backup jobs, including last run date and result, and view server status and live progress of a running task. Trigger or abort a backup job. Export, update and import job configurations as JSON. With the local database path set, read backup metadata, schedules, options, restore points, operation history, error logs and notifications from the Duplicati SQLite database.
- When to use it
- Useful when you run Duplicati and want an assistant to report on backup health, check history and restore points, or adjust job settings without clicking through the web interface. A read-only mode suits exploration and analysis without risk of changes.
- Requirements
- Runs locally as a stdio process (Python via uv) or as a Docker image with streamable HTTP on port 3000. Needs DUPLICATI_URL pointing at a reachable Duplicati instance and, if the web interface has one, DUPLICATI_PASSWORD. Network access to that instance. The db_* history tools additionally need DUPLICATI_DB_PATH pointing at Duplicati-server.sqlite, shared read-only when using Docker.
Installation
In SourceWeft
- Open Duplicati Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Duplicati MCP Server
MCP (Model Context Protocol) server for managing Duplicati backups from an LLM.
Version française / French version
Architecture
The server wraps the Duplicati REST API and exposes it via the MCP protocol. Two transports are supported:
- stdio — for local use via Claude Code (no network, no port)
- Streamable HTTP — for Docker deployment, accessible over the network
Getting Started
Local use with Claude Code (stdio)
The simplest way to get started. The .mcp.json at the project root handles everything:
Set your Duplicati URL and password in .mcp.json:
With Docker Compose (Docker Hub image)
With Docker Compose (local build)
Direct Docker usage
Verification
Client Configuration
Claude Code — local (stdio)
For local use without Docker, add to your project .mcp.json:
Credentials are loaded from the .env file at the project root (see Getting Started).
Claude Code — Docker/remote (HTTP)
Add to your .mcp.json:
Claude Desktop
Claude Desktop requires mcp-proxy as a bridge to HTTP servers. Add to your configuration file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Available Tools
Once connected, the LLM has access to:
Backup Jobs
- list_backups — List all configured jobs with ID, name, last run date and result
- get_backup — Get detailed information about a specific job
- run_backup — Trigger a backup job immediately
- abort_backup — Abort the currently running backup for a job
Status & Progress
- get_progress — Live progress of the active backup task (phase, %, file counts)
- get_server_status — Duplicati server state, version and active task
Configuration
- export_backup_config — Export a job configuration as JSON
- update_backup_config — Update an existing job configuration in place (use with
export_backup_configto modify sources, settings, schedule, etc.) - import_backup_config — Import a job configuration from JSON (creates a new job)
History & Diagnostics (SQLite — requires DUPLICATI_DB_PATH)
- db_get_backup_metadata — Rich metadata from the local database: last run date, duration, file counts, quota usage, last error
- db_get_backup_schedule — Schedule configuration for a backup job
- db_list_errors — Recent error log entries, optionally filtered by job
- db_list_notifications — System notifications (update alerts, etc.)
- db_get_backup_options — Configuration options for a job (compression, retention policy, etc.) — passphrases excluded
- db_list_operations — Operation history for a job (Backup, Restore, List, etc.) with timestamps
- db_get_operation_log — Full result and statistics for a specific operation
- db_list_filesets — Available restore points (backup versions) for a job
Example Prompts
Once the server is connected to your LLM, here are prompts you can use:
General status
- "What backup jobs are configured on my Duplicati?"
- "What was the last backup that ran and what was the result?"
- "Is a backup currently running?"
History & statistics (requires DUPLICATI_DB_PATH)
- "Show me the last 10 operations for backup job 2"
- "What is the average duration of recent backups?"
- "Have there been any errors on my backups in the past few weeks?"
- "How many files are backed up and what is the total size on the destination?"
Restore points (requires DUPLICATI_DB_PATH)
- "What restore points are available for my backup job?"
- "What is the oldest backup available for a restore?"
Configuration (requires DUPLICATI_DB_PATH)
- "What retention policy is configured on my backup job?"
- "What compression and encryption options are in use?"
Diagnostics (requires DUPLICATI_DB_PATH)
- "Are there any pending system notifications on Duplicati?"
- "Has my Duplicati encountered any errors recently? Which ones?"
- "Analyse the last backup and tell me if everything went well"
Open-ended (combines multiple tools)
- "Give me a full health report on my Duplicati backups"
Environment Variables
Read-only Mode
DUPLICATI_READONLY=true disables run_backup, abort_backup, update_backup_config and import_backup_config. All read tools remain active. Useful for safely exploring and analysing backup configurations without any risk of modification.
SQLite Access
Setting DUPLICATI_DB_PATH enables the db_* tools, which read directly from the Duplicati SQLite databases. Access is strictly read-only: databases are opened in read-only mode and copied to memory via the SQLite Online Backup API before any query — the live Duplicati databases are never locked or modified.
Local use — point to the server database on your machine:
Docker — share the Duplicati config directory as a read-only volume. In docker-compose.yml:
Docker Hub
- Repository: kcofoni/duplicati-mcp
- Latest tag:
kcofoni/duplicati-mcp:latest
Development
File Structure
Running Tests
Interactive Tool Testing (local)
Troubleshooting
Cannot connect to Duplicati
Check that DUPLICATI_URL is reachable from the container. If both run in Docker, put them on the same network and use the service name as hostname.
Authentication failed
Verify DUPLICATI_PASSWORD matches the password set in Duplicati's web interface. Leave empty if no password is configured.
MCP endpoint not responding
License
This project is licensed under the MIT License — see the LICENSE file for details.
Source: README.md at commit ab1914d
Tools
0Version history
1- v1.1.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts