Skip to main content
Glama
danielrosehill

BTRFS Snapper MCP

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SNAPPER_MCP_TIMEOUTNoCommand timeout in seconds60
SNAPPER_MCP_USE_SUDONoSet to 'false' if user has direct permissionstrue
SNAPPER_MCP_SUDO_PATHNoPath to sudo binarysudo
SNAPPER_MCP_BTRFS_PATHNoPath to btrfs binarybtrfs
SNAPPER_MCP_SNAPPER_PATHNoPath to snapper binarysnapper
SNAPPER_MCP_DEFAULT_MOUNTNoDefault BTRFS mount point/
SNAPPER_MCP_DEFAULT_CONFIGNoDefault snapper config nameroot

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
snapperA

Manage BTRFS snapshots via Snapper. A unified tool for all snapshot operations.

Actions:

  • configs: List available snapper configurations

  • list: Show all snapshots for a config

  • create: Create a new snapshot (optionally with description)

  • delete: Remove a snapshot by number

  • rollback: Restore system to a previous snapshot (requires reboot)

  • cleanup: Prune snapshots using an algorithm (number, timeline, empty-pre-post)

  • diff: Show file differences between two snapshots

  • status: List changed files between two snapshots

Current default config: root Using sudo: True

Examples:

  • List configs: action="configs"

  • List snapshots: action="list", config="root"

  • Create snapshot: action="create", config="root", description="Before update"

  • Delete snapshot: action="delete", config="root", snapshot_id=5

  • Compare snapshots: action="diff", config="root", snapshot_id=1, snapshot_id_end=5

  • Cleanup old snapshots: action="cleanup", config="root", cleanup_algorithm="number"

btrfs_healthA

Check BTRFS filesystem health and status. Monitor disk usage, errors, and maintenance operations.

Actions:

  • usage: Comprehensive filesystem space usage

  • devices: List devices in the BTRFS array

  • stats: Device error statistics (corruption, read/write errors)

  • scrub_status: Status of scrub operation (data integrity check)

  • balance_status: Status of balance operation (data redistribution)

  • df: Space allocation by data type (Data, Metadata, System)

  • filesystem_show: Filesystem information and device list

Current default mount: / Using sudo: True

Examples:

  • Check usage: action="usage", mount_point="/"

  • Check for errors: action="stats", mount_point="/"

  • Scrub status: action="scrub_status", mount_point="/"

  • Show filesystem: action="filesystem_show"

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.3/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have completely distinct purposes: btrfs_health monitors filesystem health, and snapper manages snapshots. There is no overlap in functionality, so an agent can easily distinguish when to use each.

Naming Consistency4/5

Both tool names are descriptive and use a clear style (btrfs_health uses prefix 'btrfs_', snapper uses the application name). While there is no strict pattern like verb_noun, the names are intuitive and consistent in being self-explanatory.

Tool Count2/5

Only two tools for a complex domain like BTRFS management is minimal. Each tool bundles many sub-actions, which could be separate tools for better discoverability. The low count suggests an incomplete surface for tasks like defragmentation or advanced configuration.

Completeness4/5

The tools cover essential BTRFS operations: health monitoring (usage, errors, scrub, balance) and snapshot management (create, delete, rollback, diff, cleanup). Missing are direct balance initiation or defragmentation, but these are covered by status checks, making the set fairly comprehensive for core tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues