Back to Browse

Pihole MCP Server

Developer ToolsLow Risk10.0MCP RegistryLocal
Free

Server data from the Official MCP Registry

Manage Pi-hole v6: DNS blocking, domains, clients, query analysis, DHCP, and multi-instance sync.

About

Manage Pi-hole v6: DNS blocking, domains, clients, query analysis, DHCP, and multi-instance sync.

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (3 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

5 files analyzed · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

What You'll Need

Set these up before or after installing:

Base URL of your Pi-hole web interface. For multiple Pi-holes use PIHOLE_1_URL, PIHOLE_2_URL, ... instead.Optional

Environment variable: PIHOLE_URL

Pi-hole admin password, or an application password (recommended — bypasses TOTP 2FA)Required

Environment variable: PIHOLE_PASSWORD

IANA timezone for rendered timestamps, e.g. Australia/Adelaide. Defaults to UTC in the container.Optional

Environment variable: TZ

Expose only inspection tools. Every tool that can change Pi-hole is hidden and rejected if called.Optional

Environment variable: PIHOLE_READ_ONLY

Set to true only for a Pi-hole serving a self-signed HTTPS certificate. A trusted certificate is the better fix.Optional

Environment variable: PIHOLE_TLS_SKIP_VERIFY

HTTP request timeout as a Go duration, e.g. 30s or 1mOptional

Environment variable: PIHOLE_REQUEST_TIMEOUT

Retries after a transient Pi-hole API failure; 0 disables retryingOptional

Environment variable: PIHOLE_MAX_RETRIES

Upper bound on a single exponential-backoff wait, as a Go durationOptional

Environment variable: PIHOLE_RETRY_MAX_DELAY

Reviews

No reviews yet

Be the first to review this server!