Pi-hole MCP Server

Name: Pi-hole MCP Server
Author: hexamatic

作者：hexamatic版本 0.10.0i★ –i在你的电脑上运行

注册名称io.github.hexamatic/pihole-mcp

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 开发者工具
你需要填写：PIHOLE_URL, PIHOLE_PASSWORD

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： PIHOLE_URL, PIHOLE_PASSWORD, TZ, PIHOLE_READ_ONLY, PIHOLE_TLS_SKIP_VERIFY, PIHOLE_REQUEST_TIMEOUT, PIHOLE_MAX_RETRIES, PIHOLE_RETRY_MAX_DELAY

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

Docker已安装 Docker

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "pihole": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "PIHOLE_URL",
        "-e",
        "PIHOLE_PASSWORD",
        "-e",
        "TZ",
        "-e",
        "PIHOLE_READ_ONLY",
        "-e",
        "PIHOLE_TLS_SKIP_VERIFY",
        "-e",
        "PIHOLE_REQUEST_TIMEOUT",
        "-e",
        "PIHOLE_MAX_RETRIES",
        "-e",
        "PIHOLE_RETRY_MAX_DELAY",
        "ghcr.io/hexamatic/pihole-mcp:0.10.0"
      ],
      "env": {
        "PIHOLE_URL": "your-value",
        "PIHOLE_PASSWORD": "your-value",
        "TZ": "your-value",
        "PIHOLE_READ_ONLY": "your-value",
        "PIHOLE_TLS_SKIP_VERIFY": "your-value",
        "PIHOLE_REQUEST_TIMEOUT": "your-value",
        "PIHOLE_MAX_RETRIES": "your-value",
        "PIHOLE_RETRY_MAX_DELAY": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add pihole --env PIHOLE_URL=your-value --env PIHOLE_PASSWORD=your-value --env TZ=your-value --env PIHOLE_READ_ONLY=your-value --env PIHOLE_TLS_SKIP_VERIFY=your-value --env PIHOLE_REQUEST_TIMEOUT=your-value --env PIHOLE_MAX_RETRIES=your-value --env PIHOLE_RETRY_MAX_DELAY=your-value -- docker run -i --rm -e PIHOLE_URL -e PIHOLE_PASSWORD -e TZ -e PIHOLE_READ_ONLY -e PIHOLE_TLS_SKIP_VERIFY -e PIHOLE_REQUEST_TIMEOUT -e PIHOLE_MAX_RETRIES -e PIHOLE_RETRY_MAX_DELAY ghcr.io/hexamatic/pihole-mcp:0.10.0

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "pihole": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "PIHOLE_URL",
        "-e",
        "PIHOLE_PASSWORD",
        "-e",
        "TZ",
        "-e",
        "PIHOLE_READ_ONLY",
        "-e",
        "PIHOLE_TLS_SKIP_VERIFY",
        "-e",
        "PIHOLE_REQUEST_TIMEOUT",
        "-e",
        "PIHOLE_MAX_RETRIES",
        "-e",
        "PIHOLE_RETRY_MAX_DELAY",
        "ghcr.io/hexamatic/pihole-mcp:0.10.0"
      ],
      "env": {
        "PIHOLE_URL": "your-value",
        "PIHOLE_PASSWORD": "your-value",
        "TZ": "your-value",
        "PIHOLE_READ_ONLY": "your-value",
        "PIHOLE_TLS_SKIP_VERIFY": "your-value",
        "PIHOLE_REQUEST_TIMEOUT": "your-value",
        "PIHOLE_MAX_RETRIES": "your-value",
        "PIHOLE_RETRY_MAX_DELAY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "pihole": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "PIHOLE_URL",
        "-e",
        "PIHOLE_PASSWORD",
        "-e",
        "TZ",
        "-e",
        "PIHOLE_READ_ONLY",
        "-e",
        "PIHOLE_TLS_SKIP_VERIFY",
        "-e",
        "PIHOLE_REQUEST_TIMEOUT",
        "-e",
        "PIHOLE_MAX_RETRIES",
        "-e",
        "PIHOLE_RETRY_MAX_DELAY",
        "ghcr.io/hexamatic/pihole-mcp:0.10.0"
      ],
      "env": {
        "PIHOLE_URL": "your-value",
        "PIHOLE_PASSWORD": "your-value",
        "TZ": "your-value",
        "PIHOLE_READ_ONLY": "your-value",
        "PIHOLE_TLS_SKIP_VERIFY": "your-value",
        "PIHOLE_REQUEST_TIMEOUT": "your-value",
        "PIHOLE_MAX_RETRIES": "your-value",
        "PIHOLE_RETRY_MAX_DELAY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

PIHOLE_URL 必填 env
Base URL of your Pi-hole web interface. For multiple Pi-holes use PIHOLE_1_URL, PIHOLE_2_URL, ... instead.
PIHOLE_PASSWORD 机密必填 env
Pi-hole admin password, or an application password (recommended — bypasses TOTP 2FA)
TZ env
IANA timezone for rendered timestamps, e.g. Australia/Adelaide. Defaults to UTC in the container.
PIHOLE_READ_ONLY env
Expose only inspection tools. Every tool that can change Pi-hole is hidden and rejected if called.
PIHOLE_TLS_SKIP_VERIFY env
Set to true only for a Pi-hole serving a self-signed HTTPS certificate. A trusted certificate is the better fix.
PIHOLE_REQUEST_TIMEOUT env
HTTP request timeout as a Go duration, e.g. 30s or 1m
PIHOLE_MAX_RETRIES env
Retries after a transient Pi-hole API failure; 0 disables retrying
PIHOLE_RETRY_MAX_DELAY env
Upper bound on a single exponential-backoff wait, as a Go duration

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 hexamatic 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“开发者工具”中的其他服务器比较i

星标数多于此分类中其他 4909 个服务器的 0%
发布到注册中心的时间比此分类中其他 4909 个服务器的 85% 更新
基础检查结果等于或优于此分类中其他 4909 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Pi-hole MCP Server 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：PIHOLE_URL, PIHOLE_PASSWORD

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.10.0）于6天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。

有什么可以替代它？

同一分类中有：GitHub, Desktop Commander, Cloudflare MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHub

作者：github

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

电脑或云端★ 34,245MIT4天前更新

安装

Desktop Commander

作者：wonderwhy-er

MCP server for terminal commands, file operations, and process management

在你的电脑上运行★ 10,225MIT16天前更新

安装

Cloudflare MCP

作者：cloudflare

Cloudflare MCP servers

在云端运行★ 4,446Apache-2.014个月前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

pihole-mcp

A production-grade MCP server for Pi-hole v6.

Gives AI assistants full control over your Pi-hole instance: DNS blocking, domain management, query analysis, statistics, network devices, DHCP, and system administration. Compatible with the Pi-hole v6 REST API.

Why this one

Run it locked down. PIHOLE_READ_ONLY=true exposes only the tools that cannot change anything, enforced on every call, not just the tool list a client happens to cache. PIHOLE_TOOLSETS narrows further to just the families you need, so a client asking "what can I use" gets a smaller, cheaper answer.
82 tools (84 once a second Pi-hole is configured) covering roughly 95% of the Pi-hole v6 REST API, including domains, lists, groups, clients, DHCP, network, the query log, configuration, local DNS records, teleporter backup and restore, and session management.
Multi-instance diff and sync. Compare two Pi-holes and see exactly what differs, or reconcile one onto the other with a dry-run plan and a confirm token before anything is written.
Releases are signed and attested, not just built. Every archive and container image carries a keyless cosign signature, an SPDX SBOM and SLSA build provenance, and SECURITY.md has the one-line command to check each.
Listed in the official [MCP Registry](https://registry.modelcontextprotocol.io/) as io.github.hexamatic/pihole-mcp, installable by name from any client that supports registry install.
Shipped nine releases in five months since launch, each with real release notes describing what changed and why, not a commit-hash dump.

Quick Start

Most MCP clients use the same configuration format. Add this to your client's config:

"mcpServers": { "pihole": { "command": "pihole-mcp", "env": { "PIHOLE_URL": "http://192.168.1.2", "PIHOLE_PASSWORD": "your-password" } } } }

Then install the binary via one of the methods below.

What you can ask

The whole point is natural language, not tool names. A few examples of what to actually type:

You ask	What runs
"Is Pi-hole blocking right now, and for how long?"	`pihole_dns_get_blocking`
"Pause blocking for 10 minutes, I need to test something."	`pihole_dns_set_blocking`
"Why is reddit.com blocked? Check every list it could be on."	`pihole_search_domains`
"What are the top blocked domains today, and does anything look like a false positive?"	`pihole_stats_recent_blocked`, the `review_top_blocked` prompt
"Point nas.home at 192.168.1.50."	`pihole_local_dns_add`
"Which of my blocklists haven't updated in 30+ days?"	`pihole_lists_list`
"Show me devices on the network Pi-hole doesn't recognise."	`pihole_network_devices`, the `audit_network` prompt
"Compare my two Pi-holes and tell me what's different."	`pihole_instance_diff`
"Back up my configuration before I change anything."	`pihole_teleporter_export`
"Which upstream resolver is slowest, and is it worth switching?"	`pihole_stats_upstreams`, the `upstream_health` prompt

Set PIHOLE_READ_ONLY=true first if you want to ask questions without any risk of something being changed. See Scoping the tool surface.

Installation

MCP Registry

pihole-mcp is listed in the official MCP Registry as:

io.github.hexamatic/pihole-mcp

Clients that support registry install can add it by that name and will prompt for PIHOLE_URL and PIHOLE_PASSWORD. The listing points at the ghcr.io image, so the client needs a working Docker.

Homebrew

brew install hexamatic/tap/pihole-mcp

Installs on both macOS and Linux (Homebrew on Linux). On macOS the cask clears the quarantine attribute during install, so the binary runs without a Gatekeeper prompt. From v0.10.0 the macOS binaries need macOS 13 Ventura or later; v0.9.0 is the last release that runs on macOS 12.

Scoop (Windows)

scoop bucket add hexamatic https://github.com/hexamatic/scoop-bucket

scoop install pihole-mcp

Go Install

go install github.com/hexamatic/pihole-mcp/cmd/pihole-mcp@latest

Docker

docker pull ghcr.io/hexamatic/pihole-mcp:latest

Linux Packages

.deb and .rpm packages for Debian-based (Ubuntu, Raspberry Pi OS) and RPM-based (Fedora, RHEL) distributions are available on the Releases page.

# Debian / Ubuntu / Raspberry Pi OS

sudo dpkg -i pihole-mcp_X.Y.Z_linux_amd64.deb

Fedora / RHEL / CentOS

sudo rpm -i pihole-mcp_X.Y.Z_linux_amd64.rpm

Binary Download

Pre-built binaries for Linux, macOS 13 or later, and Windows (amd64 and arm64) are available on the Releases page.

Releases are checksummed, signed with keyless cosign, and ship SPDX SBOMs and SLSA build provenance. See SECURITY.md for the verification commands.

Check your setup

Once installed and configured, run the server directly with -check. It loads the configuration, contacts every Pi-hole you have configured, and reports each one by name:

PIHOLE_URL=http://192.168.1.2 PIHOLE_PASSWORD=your-password pihole-mcp -check

pihole-mcp 0.10.0

PASS primary (http://192.168.1.2) core v6.5, FTL v6.8

All 1 instance(s) reachable and authenticated.

It exits non-zero if any instance fails, and prints what to change. It also warns when a Pi-hole runs an FTL release affected by published security advisories, naming the release that fixes them. Worth running before you wire the server into a client: most clients hide the server's output, so a bad URL or password looks the same as a server that never started.

Configuration

Variable	Required	Default	Description
`PIHOLE_URL`	Yes	-	Pi-hole base URL (e.g. `http://192.168.1.2`)
`PIHOLE_PASSWORD`	Yes	-	Admin password or application password
`PIHOLE_READ_ONLY`	No	`false`	Expose only tools that cannot change Pi-hole. See Scoping the tool surface.
`PIHOLE_TOOLSETS`	No	all	Comma-separated toolset names to expose, e.g. `dashboard,domains`. Unset or `all` exposes everything.
`PIHOLE_REQUEST_TIMEOUT`	No	`30s`	HTTP request timeout
`PIHOLE_MAX_RETRIES`	No	`3`	Retries after a failed Pi-hole API call. `0` disables.
`PIHOLE_RETRY_MAX_DELAY`	No	`8s`	Upper bound on a single backoff wait.
`PIHOLE_HTTP_AUTH_TOKEN`	No	-	Shared bearer token required on every HTTP/SSE request. Minimum 16 characters. Unset means no authentication.
`PIHOLE_HTTP_AUTH_TOKEN_FILE`	No	-	Path to a file holding the bearer token, so it stays out of `ps`. Mutually exclusive with `PIHOLE_HTTP_AUTH_TOKEN`.
`PIHOLE_RATE_LIMIT`	No	`120`	Requests per minute per MCP session on the HTTP/SSE transports, under a per-address ceiling of four times that. Clients on MCP revision `2026-07-28` send no session, so only the ceiling applies to them. `0` disables.
`PIHOLE_ALLOWED_ORIGINS`	No	`localhost,127.0.0.1,[::1]`	Comma-separated Origin/Host allowlist for HTTP/SSE transports. The literal `*` disables enforcement (unsafe). Not authentication.
`PIHOLE_TRUSTED_PROXIES`	No	-	Comma-separated IPs or CIDR blocks whose `X-Forwarded-For` the rate limiter believes. Unset means the header is ignored.
`PIHOLE_BACKUP_DIR`	No	-	Absolute path of an existing directory to keep teleporter backups in. When set, `pihole_teleporter_export` writes only inside it and `pihole_teleporter_import` reads only from it, and the server never removes anything there. Unset, backups go to the system temp directory by default, where the server removes its own after a day, and any absolute path is accepted.
`PIHOLE_TLS_SKIP_VERIFY`	No	`false`	Disable TLS certificate verification for Pi-hole connections. Only for instances serving self-signed certificates. A trusted certificate is preferable where possible.
`TZ`	No	System timezone (UTC in Docker)	IANA timezone for rendered timestamps (e.g. `Australia/Adelaide`). Timezone data is embedded in the binary, so this works in the Docker image out of the box.
`OTEL_EXPORTER_OTLP_ENDPOINT`	No	-	OpenTelemetry collector endpoint. Setting it enables tracing; ignored in slim builds.

Application passwords are recommended for automation: they bypass TOTP 2FA and can be revoked independently.

PIHOLE_HTTP_AUTH_TOKEN, PIHOLE_HTTP_AUTH_TOKEN_FILE, PIHOLE_RATE_LIMIT, PIHOLE_ALLOWED_ORIGINS and PIHOLE_TRUSTED_PROXIES only apply to the http and sse transports; stdio is a single-process, single-user channel by definition and isn't gated. See Security before exposing either transport beyond loopback.

Scoping the tool surface

By default the server offers every tool, including 34 that change Pi-hole and 27 that are destructive. Two variables narrow that.

PIHOLE_READ_ONLY=true exposes only tools that cannot change anything, on Pi-hole or on the host the server runs on, so it leaves out pihole_teleporter_export, which writes a file. Write tools are absent from tools/list and rejected if called anyway, so a client working from a cached listing cannot reach one either.

PIHOLE_READ_ONLY=true    # 48 tools instead of 82

PIHOLE_TOOLSETS selects which families of tools exist at all, which is worth doing on its own because tools/list is a cost paid in every conversation:

PIHOLE_TOOLSETS=dashboard,domains,lists    # blocklist curation, and nothing else

PIHOLE_TOOLSETS=all # the default, stated explicitly

The two intersect, and read-only always wins. PIHOLE_READ_ONLY=true with PIHOLE_TOOLSETS=dns,stats gives the 14 tools that are in those toolsets *and* read-only.

The toolset names, what each contains and how many tools it holds are in docs/TOOLS.md, generated from the same table the server filters with. An unknown name fails at startup and lists every valid one; run pihole-mcp -check to see it, along with how many tools your configuration actually exposes:

scope: read-only=true, toolsets=dns,stats  14 of 82 tools exposed

A published toolset name is never removed, renamed or narrowed. See CONTRIBUTING.md for the full promise.

Multiple instances

To manage more than one Pi-hole, configure numbered instances instead of PIHOLE_URL/PIHOLE_PASSWORD:

Variable	Required	Description
`PIHOLE_1_URL`, `PIHOLE_2_URL`, …	Yes	Base URL of each instance (contiguous from 1)
`PIHOLE_1_PASSWORD`, `PIHOLE_2_PASSWORD`, …	Yes	Password for the matching instance

| PIHOLE_1_NAME, PIHOLE_2_NAME, … | No | Fri

只显示了开头部分；其余内容请在仓库中阅读