Bareos Mcp Server

Name: Bareos Mcp Server
Author: edeckers

@edeckers

About Bareos Mcp Server

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

#backups #bareos

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

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

Tools

List backup jobs with filters

Get detailed status of a job

View complete job log

List files backed up in a job

List all file daemon clients

List backup filesets

List storage pools

List volumes/media

Overview

What is Bareos Mcp Server?

A Model Context Protocol server providing read-only operations for monitoring and querying the Bareos backup system via bconsole. Intended for administrators who want to interact with their backup infrastructure through AI assistants.

How to use Bareos Mcp Server?

Clone the repository, build with cargo, ensure bconsole is accessible (locally, via SSH wrapper, or Docker), then configure your MCP client (Claude Code or Claude Desktop) with the binary path and optional BAREOS_BCONSOLE_PATH environment variable. Use natural language queries to inspect jobs, clients, filesets, pools, and volumes.

Key features of Bareos Mcp Server

Read-only operations – safe for production environments
List and filter backup jobs with multiple parameters
View detailed job status and logs
List clients, filesets, pools, and volumes
Supports time filters (days/hours) and output modes (last/count)

Use cases of Bareos Mcp Server

Check recent backup job status and logs
Count failed backups within a time window
List all Bareos file daemon clients
Monitor pool capacity and volumes ready for pruning
Retrieve backup filesets and storage pool details

FAQ from Bareos Mcp Server

What are the prerequisites to run Bareos Mcp Server?

Rust 1.70+ for building, a Bareos Director with bconsole access, and the bconsole command-line utility.

How do I connect to a remote Bareos Director?

Create an SSH wrapper script that executes bconsole on the remote host, then set BAREOS_BCONSOLE_PATH to point to that script or ensure it’s in your PATH.

How can I test the server without an MCP client?

You can pipe JSON-RPC requests directly to the compiled binary (e.g., for initialization, listing tools, or calling list_jobs). Examples are provided in the README.

What tools does the server expose?

Seven tools: list_jobs, get_job_status, get_job_log, list_files, list_clients, list_filesets, list_pools, and list_volumes. All are read-only.

What if I get a "bconsole not found" or "permission denied" error?

Ensure bconsole is in your PATH or set BAREOS_BCONSOLE_PATH. Check that your user has permissions to read bconsole.conf or is in the bareos group. Verify the Director service is running and reachable.