BTRFS Snapper MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SNAPPER_MCP_TIMEOUT | No | Command timeout in seconds | 60 |
| SNAPPER_MCP_USE_SUDO | No | Set to 'false' if user has direct permissions | true |
| SNAPPER_MCP_SUDO_PATH | No | Path to sudo binary | sudo |
| SNAPPER_MCP_BTRFS_PATH | No | Path to btrfs binary | btrfs |
| SNAPPER_MCP_SNAPPER_PATH | No | Path to snapper binary | snapper |
| SNAPPER_MCP_DEFAULT_MOUNT | No | Default BTRFS mount point | / |
| SNAPPER_MCP_DEFAULT_CONFIG | No | Default snapper config name | root |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| snapperA | Manage BTRFS snapshots via Snapper. A unified tool for all snapshot operations. Actions:
Current default config: root Using sudo: True Examples:
|
| btrfs_healthA | Check BTRFS filesystem health and status. Monitor disk usage, errors, and maintenance operations. Actions:
Current default mount: / Using sudo: True Examples:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
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.
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.
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.
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.