backrest-mcp
MCP server for Backrest that provides read-only and gated write access to backup configuration, snapshots, and operations, with layered safety controls to protect backup data.
README
backrest-mcp
MCP server for Backrest — a web UI and orchestrator for restic backups.
Python/FastMCP rewrite of backrest-mcp-server. Covers the full useful surface of the Backrest REST API with layered safety controls to protect backup data.
Tools
| Tool | Description | Requires |
|---|---|---|
get_config |
Read Backrest configuration (repos, plans) | — |
list_snapshots |
List snapshots, optionally filtered by repo or plan | — |
list_snapshot_files |
Browse files within a snapshot | — |
get_summary |
30-day dashboard stats per repo and plan | — |
get_operations |
Recent operation history with status icons | — |
trigger_backup |
Trigger a backup plan (dry_run supported) | BACKREST_READONLY=false |
do_repo_task |
Run maintenance: prune/check/stats/unlock/index | BACKREST_READONLY=false |
cancel_operation |
Cancel a running operation | BACKREST_READONLY=false |
forget_snapshot |
Permanently forget a snapshot (confirm token required) | BACKREST_ALLOW_DESTRUCTIVE=true |
restore_snapshot |
Restore snapshot to a staging path | BACKREST_ALLOW_DESTRUCTIVE=true |
Default state: read-only — only the top 5 tools are registered. No write calls are possible without explicit opt-in.
Safety Controls
Backups are critical data. Four controls gate write and destructive operations:
1. Read-only mode (default: on)
BACKREST_READONLY=true # no write tools registered (default)
BACKREST_READONLY=false # enables trigger_backup, do_repo_task, cancel_operation
2. Destructive gate (default: off)
BACKREST_ALLOW_DESTRUCTIVE=false # forget/restore never registered (default)
BACKREST_ALLOW_DESTRUCTIVE=true # enables forget_snapshot, restore_snapshot
# requires BACKREST_READONLY=false
3. Forget confirmation token
forget_snapshot requires confirm=f"FORGET:{snapshot_id}". The caller must name the exact snapshot being deleted.
4. Restore path guard
restore_snapshot validates the target path against BACKREST_RESTORE_ALLOWED_PREFIX (default: /tmp/backrest-restore/) using os.path.realpath(). Path traversal attempts are blocked. After verifying restored files, move them manually.
5. Audit log
Set BACKREST_AUDIT_LOG=/path/to/audit.jsonl to log all write operations. Credential values are never included.
Configuration
| Env var | Default | Purpose |
|---|---|---|
BACKREST_URL |
http://localhost:9898 |
Backrest base URL |
BACKREST_USERNAME |
— | Basic Auth username (optional) |
BACKREST_PASSWORD |
— | Basic Auth password |
BACKREST_READONLY |
true |
Disable all write tools |
BACKREST_ALLOW_DESTRUCTIVE |
false |
Enable forget/restore (requires READONLY=false) |
BACKREST_RESTORE_ALLOWED_PREFIX |
/tmp/backrest-restore/ |
Restore target path guard |
BACKREST_AUDIT_LOG |
— | JSONL audit log for write ops |
LOG_LEVEL |
INFO |
Logging verbosity |
LOG_FILE |
stderr | Log file path |
INFLUXDB_URL |
— | Optional InfluxDB metrics |
Install
python3 -m venv .venv
source .venv/bin/activate
pip install -e .
For development/testing:
pip install -e ".[dev]"
pytest
Deployment (PM2)
An ecosystem.config.js is included for PM2-managed deployment. Credentials are injected
via --env-file to avoid storing them in the config file:
cd /path/to/backrest-mcp
pm2 start ecosystem.config.js --env-file /path/to/secrets.env
The secrets file must contain BACKREST_USERNAME and BACKREST_PASSWORD. All other settings
default safely in ecosystem.config.js (BACKREST_READONLY=true, BACKREST_ALLOW_DESTRUCTIVE=false).
The server runs in stdio mode via the backrest-mcp entry point. To expose over HTTP,
use a FastMCP HTTP wrapper or proxy.
Claude Desktop Config
{
"mcpServers": {
"backrest": {
"command": "/path/to/backrest-mcp/.venv/bin/python",
"args": ["-m", "backrest_mcp.server"],
"env": {
"BACKREST_URL": "http://localhost:9898",
"BACKREST_USERNAME": "your-username",
"BACKREST_PASSWORD": "your-password",
"BACKREST_READONLY": "true"
}
}
}
}
Omit BACKREST_USERNAME and BACKREST_PASSWORD if Backrest auth is disabled.
TLS
If connecting to an HTTPS endpoint with a private or self-signed CA:
REQUESTS_CA_BUNDLE=/path/to/ca.crt
httpx respects this env var. Do not disable TLS verification.
Observability
Structured JSON logs via structlog. LOG_LEVEL controls verbosity (default: INFO). Set
LOG_FILE to write to a file instead of stderr.
Optional InfluxDB metrics via pip install -e ".[influxdb]":
| Env var | Purpose |
|---|---|
INFLUXDB_URL |
InfluxDB write URL |
INFLUXDB_TOKEN |
Auth token |
INFLUXDB_ORG |
Organization |
INFLUXDB_BUCKET |
Bucket (default: backrest) |
Each tool call emits a backrest_tool measurement with tool tag and duration_ms field.
Auth Architecture
Credentials flow: env vars → BackrestClient.__init__ → httpx Basic Auth tuple → Authorization header.
Credentials are never written to logs, audit entries, or MCP tool responses.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.