Log inSubmit server
Duplicacy MCP logo

Duplicacy MCP

by GeiserX

Monitors Duplicacy backups through exporter metrics, with MCP tools for status, history, snapshots, and pruning.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Duplicacy MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "geiserx-duplicacy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "duplicacy-mcp"
      ],
      "env": {
        "DUPLICACY_EXPORTER_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

GeiserX/duplicacy-mcp connects MCP clients to metrics collected by the Duplicacy exporter. It provides read-only status, progress, and health resources alongside tools for backup status, history, snapshots, and prune status. Run it through the `/mcp` HTTP endpoint, stdio via npm, Docker, or a platform-specific Go binary when an agent needs access to Duplicacy backup monitoring data.

Use cases

  • Check current Duplicacy backup status from an MCP client
  • Review backup history and snapshot availability
  • Inspect exporter-derived progress and health information
  • Monitor prune status through agent tools

Key features

  • Reads metrics from duplicacy-exporter
  • Provides backup status and history queries
  • Lists Duplicacy snapshots
  • Reports prune status
  • Exposes read-only status, progress, and health resources
  • Supports HTTP JSON-RPC and stdio transport

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

7/7 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · duplicacy-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2Stargazers on the source repository.
npm downloads235Package downloads in the last 30 days.
Last commit8d agoMost recent push to the default branch.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Duplicacy MCP works

What GeiserX/duplicacy-mcp MCP server does

GeiserX/duplicacy-mcp bridges a Duplicacy Prometheus exporter and MCP-compatible clients. It reads the exporter’s backup metrics and makes them available for agent-driven monitoring of backup state, progress, and health.

The server is intended for read-oriented inspection rather than backup administration. It exposes three MCP resources—duplicacy://status, duplicacy://progress, and duplicacy://health—for browsing current monitoring information. Four tools provide more targeted queries: get_backup_status, get_backup_history, list_snapshots, and get_prune_status.

How it works

The MCP process retrieves metrics from duplicacy-exporter, whose endpoint is supplied through configuration. Clients can communicate with the server over a single JSON-RPC endpoint at /mcp, or start it as a local stdio process through the npm package.

The HTTP mode listens on 127.0.0.1:8080 by default. This keeps the default listener local; deployments that make the endpoint reachable beyond the host should place an authenticated reverse proxy in front of it.

Setup and configuration

The server can be run as a Docker container, through the npm package, or from one of the published Go binaries. A Docker deployment maps the local port to port 8080 and sets DUPLICACY_EXPORTER_URL to the exporter address, such as http://duplicacy-exporter:9750.

For stdio clients, configure the npm package as the command and pass -y duplicacy-mcp as its arguments. The exporter URL is supplied in the client’s environment configuration. A local build and Docker Compose setup are also available as deployment options.

The HTTP endpoint is available at http://127.0.0.1:8080/mcp with the default listener settings. The project also distributes an npm wrapper, Docker image, and Go binaries for multiple platforms.

Tools and capabilities

  • get_backup_status queries backup job status.
  • get_backup_history retrieves historical backup information.
  • list_snapshots lists available Duplicacy snapshots.
  • get_prune_status reports pruning status.
  • duplicacy://status provides a read-only status resource.
  • duplicacy://progress provides a read-only progress resource.
  • duplicacy://health provides a read-only health resource.

Together, these interfaces cover current backup state, progress, health, historical activity, snapshots, and pruning information derived from the exporter.

Limitations and notes

The server depends on a reachable Duplicacy exporter and uses its metrics as the source of monitoring data. It is designed to expose monitoring information through MCP; the listed resources are read-only. The default HTTP listener is local to the machine, and an authentication-capable reverse proxy is recommended before exposing the endpoint more broadly.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Duplicacy MCP

GeiserX/duplicacy-mcp is an MCP server that connects MCP clients to metrics from a Duplicacy Prometheus exporter. Its main tools query backup status and history, list snapshots, and report prune status, while read-only resources expose current status, progress, and health information.

Install it with the published npm package, Docker image, or a platform-specific Go binary. For stdio, configure `npx -y duplicacy-mcp`; for HTTP, run the container or binary and connect to `/mcp`.

Set `DUPLICACY_EXPORTER_URL` to the address of the Duplicacy exporter. The default HTTP listener is `127.0.0.1:8080`, and the MCP endpoint is `/mcp`.

It can query backup status and history, list snapshots, and report prune status. It also exposes read-only resources for Duplicacy status, progress, and health.

Related MCP servers

All in Monitoring All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewDuplicacy MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/geiserx-duplicacy-mcp?style=directory)](https://allmcps.com/mcp/geiserx-duplicacy-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/geiserx-duplicacy-mcp"><img src="https://allmcps.com/api/badge/geiserx-duplicacy-mcp?style=directory" alt="Duplicacy MCP on AllMCPs" /></a>