Bareos MCP Server

A Model Context Protocol (MCP) server for Bareos backup system, providing read-only operations for monitoring and querying backup infrastructure.

Quick Start

Once configured, ask your AI assistant naturally about your backups:

"Show me the last 10 backup jobs"
"Are there any failed backups today?"
"What's the status of job 12345?"
"How much storage is left in the Full pool?"
"List all volumes ready for pruning"

Features

Read-Only Operations

• Jobs: List recent jobs, get detailed status, view job logs
• Clients: List all Bareos file daemon clients
• Filesets: List configured backup filesets
• Storage: List pools and volumes with capacity info

All operations are read-only by design for safety in production environments.

Prerequisites

• Rust 1.70+ - For building the server
• Bareos Director - With bconsole access
• bconsole - Command-line interface to Bareos Director

Installation

1. Clone and Build

git clone https://github.com/edeckers/bareos-mcp-server.git
cd bareos-mcp-server
cargo build --release

The binary will be at: target/release/bareos-mcp-server

2. Configure bconsole Access

The MCP server calls bconsole to interact with the Bareos Director. By default it looks for bconsole in your PATH, but you can set the BAREOS_BCONSOLE_PATH environment variable to specify an absolute path to the binary or wrapper script:

export BAREOS_BCONSOLE_PATH=/usr/sbin/bconsole

You can also pass this through your MCP client config (see step 3).

You have several options:

Option A: Local bconsole (Direct Access)

If bconsole is installed locally and you have access:

# Test that bconsole works
bconsole -c /etc/bareos/bconsole.conf

No additional setup needed - the server will use bconsole directly.

Option B: Remote Bareos via SSH

If your Bareos Director is on a remote host, create a wrapper script:

# Copy the example
cp bconsole.example.sh bconsole
chmod +x bconsole

# Edit bconsole and set your hostname
vim bconsole

Example wrapper content:

#!/usr/bin/env bash
ssh your-bareos-host "sudo bconsole $*"

Add the wrapper directory to your PATH or reference it in the MCP config.

Option C: Docker/Container Setup

Run bconsole in a container that has network access to your Bareos Director.

3. Configure MCP Client

For Claude Code (CLI)

Create .mcp.json in your project directory:

cp .mcp.json.example .mcp.json
# Edit with your paths
vim .mcp.json

Example config:

{
  "bareos": {
    "command": "/absolute/path/to/bareos-mcp-server/target/release/bareos-mcp-server",
    "args": [],
    "env": {
      "BAREOS_BCONSOLE_PATH": "/absolute/path/to/bconsole"
    }
  }
}

For Claude Desktop

Add to your Claude Desktop config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "bareos": {
      "command": "/absolute/path/to/bareos-mcp-server/target/release/bareos-mcp-server",
      "args": [],
      "env": {
        "BAREOS_BCONSOLE_PATH": "/absolute/path/to/bconsole"
      }
    }
  }
}

Usage

With Claude Code

cd your-project
claude

Example queries:

• "Show me the last 10 backup jobs"
• "What's the status of job 12345?"
• "List all Bareos clients"
• "How much storage is in the Full pool?"
• "Show me volumes ready for pruning"

Available Tools

| Tool | Description | Parameters | |------|-------------|------------| | list_jobs | List backup jobs with filters | job,

... View full README on GitHub