Pi-hole MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PIHOLE_MCP_CONFIG_DIR | No | Configuration directory | ~/.local/share/pihole-mcp-server |
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 |
|---|---|
| pihole_statusA | Get Pi-hole status and statistics |
| pihole_enableB | Enable Pi-hole DNS blocking |
| pihole_disableB | Disable Pi-hole DNS blocking |
| pihole_versionA | Get Pi-hole version information |
| pihole_test_connectionA | Test Pi-hole connection and authentication |
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 5 tools
Each tool has a clearly distinct purpose: disable, enable, status, test connection, and version. No overlap in functionality.
All tools follow the pihole_ prefix with a consistent verb or noun pattern (disable, enable, status, test_connection, version). Naming is uniform and predictable.
5 tools is well-scoped for a Pi-hole server covering core operations. Not too few or too many for the domain.
Covers essential enable/disable/status/version operations. Missing detailed statistics or query list, but these are not critical for a basic management server.