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.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。