MCP server for Bareos backup system. Query your backups via your favorite AI assistant
{
"mcpServers": {
"bareos-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Model Context Protocol (MCP) server for Bareos backup system, providing read-only operations for monitoring and querying backup infrastructure.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
MPL-2.0. View license →
Is it maintained?
Last commit 38 days ago. 1 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Dynamic problem-solving through sequential thought chains
A Model Context Protocol server for searching and analyzing arXiv papers
An open-source AI agent that brings the power of Gemini directly into your terminal.
The official Python SDK for Model Context Protocol servers and clients
MCP Security Weekly
Get CVE alerts and security updates for Bareos Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server for Bareos backup system, providing read-only operations for monitoring and querying backup infrastructure.
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"
All operations are read-only by design for safety in production environments.
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
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:
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.
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.
Run bconsole in a container that has network access to your Bareos Director.
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"
}
}
}
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"
}
}
}
}
cd your-project
claude
Example queries:
| Tool | Description | Parameters |
|------|-------------|------------|
| list_jobs | List backup jobs with filters | job,