pihole-mcp
Provides tools for managing Pi-hole v6 DNS ad-blocker instances, including query logs, allow/deny lists, group management, gravity reload, blocking control, statistics, and local DNS records.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
pihole-mcp
An MCP (Model Context Protocol) server that gives AI assistants like Claude full control over your Pi-hole v6 DNS ad-blocker - query logs, allow/deny lists, group management, gravity reload, and stats. Designed from day one for multi-instance deployments: manage one or many Pi-hole instances from a single MCP endpoint.
Why?
Pi-hole's admin API is powerful but cumbersome to script against. This MCP server turns every Pi-hole API action into a tool that any MCP-compatible AI assistant can call directly. Instead of clicking through the admin UI or writing curl commands, just ask your AI to check what's being blocked, allowlist a domain, or compare stats across instances.
Perfect for homelabbers running multiple Pi-holes (primary + secondary, or per-VLAN), network admins managing DNS filtering at scale, and anyone who wants AI-assisted DNS management.
Related MCP server: MCP Pi-hole Server
Features
Multi-instance support - configure 1 to N Pi-hole instances via environment variables
Full Pi-hole v6 API coverage - query logs, allow/deny lists (full CRUD), group and client management, blocking control, local DNS (A + CNAME) records, gravity reload, stats
Smart regex detection - automatically routes domains to exact or regex lists based on metacharacter analysis
Regex landmine detector - finds deny-exact entries that look like they should be regex (miscategorized rules)
Docker-ready - multi-stage Dockerfile with non-root user, health checks, and security hardening
Streamable HTTP or stdio transport - run as a long-lived HTTP service, or let the MCP client spawn it on demand
Docker secrets support - passwords via env vars or
/run/secrets/files
Quick Start
Docker (recommended)
git clone https://github.com/ranklancer/pihole-mcp.git
cd pihole-mcp
cp .env.example .env
# Edit .env with your Pi-hole URL(s) and password(s)
mkdir -p secrets
echo "your-pihole-password" > secrets/pihole_password
chmod 600 secrets/pihole_password
openssl rand -hex 32 > secrets/mcp_auth_token # bearer token for /mcp
cp docker-compose.example.yml docker-compose.yml
docker compose up -dNode.js
npm install
npm run build
export PIHOLE_INSTANCES=pihole
export PIHOLE_BASE_URL=http://pihole.example.com
export PIHOLE_PASSWORD=your-password
npm startLocal on demand (stdio, no Docker)
The MCP client starts the server as a child process when needed and talks to it over stdin/stdout. No port is opened and nothing keeps running in the background.
npm ci
npm run build
cp .env.example .env
chmod 600 .env
# Edit .env with your Pi-hole URL(s) and password(s)Register it with Claude Code (user scope):
claude mcp add --scope user pihole -- bash -c \
'set -a; . ~/path/to/pihole-mcp/.env; set +a; MCP_TRANSPORT=stdio exec node ~/path/to/pihole-mcp/dist/index.js'Or add it manually to your MCP client config:
{
"mcpServers": {
"pihole": {
"type": "stdio",
"command": "bash",
"args": ["-c", "set -a; . ~/path/to/pihole-mcp/.env; set +a; MCP_TRANSPORT=stdio exec node ~/path/to/pihole-mcp/dist/index.js"]
}
}
}HOST and PORT from .env are ignored in stdio mode.
Configuration
All configuration is via environment variables. See .env.example for the full reference.
Single Instance
PIHOLE_INSTANCES=pihole
PIHOLE_BASE_URL=http://192.0.2.100
PIHOLE_PASSWORD=your-passwordMultiple Instances
PIHOLE_INSTANCES=primary,secondary
PRIMARY_BASE_URL=http://192.0.2.100
PRIMARY_PASSWORD=password1
SECONDARY_BASE_URL=https://198.51.100.101
SECONDARY_PASSWORD=password2
SECONDARY_INSECURE_TLS=trueFor each instance name in PIHOLE_INSTANCES, provide:
Variable | Required | Description |
| Yes | Pi-hole base URL (e.g. |
| Yes | Pi-hole API password (or use Docker secrets) |
| No | Set |
Docker secrets are supported as a fallback: /run/secrets/<name>_password (lowercase).
Available MCP Tools
Tool | Description |
| Fetch query log with filters (limit, time range, client IP or name, domain, status) |
| Add to allowlist (auto-detects exact vs regex) |
| Add to denylist (auto-detects exact vs regex) |
| List all allowlist entries (exact + regex merged) |
| List all denylist entries (exact + regex merged) |
| Get Pi-hole statistics summary |
| Trigger gravity reload |
| CRUD operations on Pi-hole groups |
| CRUD operations on Pi-hole clients and their group assignments |
| Detect miscategorized regex in deny-exact list |
| Enable/disable blocking, with optional auto-revert timer |
| Update or delete an allow/deny domain (completes CRUD) |
| List/add/delete local DNS A records |
| List/add/delete local CNAME records |
Every tool accepts an optional instance parameter to target a specific Pi-hole. Defaults to the first configured instance.
Connecting to Your MCP Client
This section applies to the HTTP transport (Docker or npm start). For stdio, see Local on demand.
The server listens on http://HOST:PORT/mcp (default: http://127.0.0.1:3000/mcp). See HTTP transport security before exposing it beyond loopback.
Claude Desktop / Claude Code
Add to your MCP settings:
{
"mcpServers": {
"pihole": {
"url": "http://localhost:3031/mcp"
}
}
}If you set a bearer token, send it in the Authorization header. Claude Code expands environment variables in .mcp.json, so the token stays out of the file:
{
"mcpServers": {
"pihole": {
"type": "http",
"url": "http://localhost:3031/mcp",
"headers": { "Authorization": "Bearer ${PIHOLE_MCP_TOKEN}" }
}
}
}HTTP transport security
These tools can disable blocking and delete domains and DNS records, so the HTTP endpoint is locked down by default, following the MCP Streamable HTTP security requirements:
Variable | Default | Effect |
|
| Bind address. |
| unset | Must be |
| unset | A non-loopback bind also needs a token (below); without one the server refuses to start unless this is |
| none | Extra hostnames accepted in the |
| none | Exact browser origins (e.g. |
| unset | Path to a file holding a bearer token (e.g. a Docker secret at |
| unset | Same, read from the environment. Set only one of the two. Prefer the file form. |
The token is compared in constant time and is never logged. There is no CLI flag for it by design.
/health needs no token (so container health checks need no secret) and returns only static service metadata; the Host and Origin checks still apply to it.
Behind a reverse proxy that forwards Host: 127.0.0.1/localhost, the Host check cannot tell proxied traffic apart, so set a token there.
On a loopback bind the token is optional. On any other bind it is required unless you set MCP_ALLOW_UNAUTHENTICATED=true, in which case the server logs a warning at startup.
Upgrading from 0.3.0 (behaviour change)
The default
HOSTchanged from0.0.0.0to127.0.0.1. A non-Docker install that relied on the old default, or setsHOST=0.0.0.0in.env, must now also setMCP_ALLOW_NON_LOOPBACK=true, or the server exits with an error saying so.Docker users must act. A non-loopback bind (which the image uses) now needs a bearer token: create
secrets/mcp_auth_tokenand setMCP_AUTH_TOKEN_FILE(the example compose file does both), then send the token from your MCP client. Or setMCP_ALLOW_UNAUTHENTICATED=trueto keep the old open behaviour. Without either, the container exits at startup with a message naming both options.Hostheaders are now validated. If clients reach the server by a LAN IP, hostname or Docker service name (rather thanlocalhost/127.0.0.1), add it toMCP_ALLOWED_HOSTSor requests get403 Invalid Host.Requests from a browser origin not in
MCP_ALLOWED_ORIGINSnow get403.
Health Check
curl http://localhost:3031/health
# {"ok":true,"service":"pihole-mcp","version":"0.3.0"}/health is unauthenticated; see HTTP transport security.
Development
npm install
npm run dev # Watch mode — recompiles on save
npm start # Run the serverRequirements
Node.js >= 20
Pi-hole v6 with API access enabled
Network connectivity to your Pi-hole instance(s)
Related Projects
Pi-hole — Network-wide ad blocking
Model Context Protocol — Open standard for AI tool integration
MCP Server Registry — Directory of MCP servers
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Connects AI assistants to TrackingTime for querying time entries, projects, tasks, customers, and team data using natural language.
Query your Logspot analytics, companies, and revenue from any AI assistant, and run your actions.
Query your Leapio analytics, companies, and revenue from any AI assistant, and run your actions.
Lets Claude, ChatGPT, and Muse read and update your beckett tasks, notes, calendar, and lists.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA server that exposes Pi-hole functionality as tools for AI assistants, allowing them to retrieve local DNS settings and query history through natural language.11MIT
- AlicenseAqualityDmaintenanceConnects AI assistants to Pi-hole network-wide ad blocker, enabling monitoring of DNS traffic statistics, controlling blocking settings, managing whitelist/blacklist domains, viewing query logs, and performing maintenance tasks through natural language.1681 npm8MIT
- FlicenseNot gradedqualityDmaintenanceEnables control of Pi-hole v6 ad blocking, allowing users to toggle DNS blocking status and retrieve real-time statistics like query counts and blocked domains. It provides a structured interface for monitoring and managing network-level ad filtering through the Pi-hole REST API.-
- AlicenseAqualityDmaintenanceEnables management of Pi-hole DNS servers through natural language commands, including enabling/disabling blocking, viewing statistics, and configuration.5MIT