Pi-hole MCP Server

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

What does this entry provide?

Pi-hole MCP Server is an MCP server entry in ChatHome Skills, sourced from Official MCP Registry and scored 73/100. As a Model Context Protocol server, it exposes tools that MCP-compatible LLM clients such as Claude, Cursor, and Copilot can call directly, extending an agent's reach beyond its built-in capabilities. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding Pi-hole MCP Server to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.

Snapshot facts

Source: Official MCP Registry
Quality: 73/100
Install method: oci
Repo: hexamatic/pihole-mcp
Repo updated: Sep 11, 2026

Install command

docker run -i --rm ghcr.io/hexamatic/pihole-mcp:0.9.0

Install method: oci

Review the upstream source before running this command.

GitHub project

Quality

Repo stars

Repo updated

Sep 11, 2026

How is this score calculated?

Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.

MCP manifest

{
  "_meta": {
    "io.modelcontextprotocol.registry/official": {
      "status": "active",
      "isLatest": true,
      "updatedAt": "2026-09-11T04:51:05.017914Z",
      "publishedAt": "2026-09-11T04:51:05.017914Z",
      "statusChangedAt": "2026-09-11T04:51:05.017914Z"
    }
  },
  "server": {
    "name": "io.github.hexamatic/pihole-mcp",
    "icons": [
      {
        "src": "https://raw.githubusercontent.com/hexamatic/pihole-mcp/main/assets/logo-256.png",
        "sizes": [
          "256x256"
        ],
        "mimeType": "image/png"
      },
      {
        "src": "https://raw.githubusercontent.com/hexamatic/pihole-mcp/main/assets/logo-120.png",
        "sizes": [
          "120x120"
        ],
        "mimeType": "image/png"
      },
      {
        "src": "https://raw.githubusercontent.com/hexamatic/pihole-mcp/main/assets/logo.svg",
        "sizes": [
          "any"
        ],
        "mimeType": "image/svg+xml"
      }
    ],
    "title": "Pi-hole MCP Server",
    "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
    "version": "0.9.0",
    "packages": [
      {
        "transport": {
          "type": "stdio"
        },
        "identifier": "ghcr.io/hexamatic/pihole-mcp:0.9.0",
        "registryType": "oci",
        "environmentVariables": [
          {
            "name": "PIHOLE_URL",
            "format": "string",
            "isRequired": true,
            "description": "Base URL of your Pi-hole web interface. For multiple Pi-holes use PIHOLE_1_URL, PIHOLE_2_URL, ... instead.",
            "placeholder": "http://192.168.1.2"
          },
          {
            "name": "PIHOLE_PASSWORD",
            "format": "string",
            "isSecret": true,
            "isRequired": true,
            "description": "Pi-hole admin password, or an application password (recommended — bypasses TOTP 2FA)"
          },
          {
            "name": "TZ",
            "format": "string",
            "description": "IANA timezone for rendered timestamps, e.g. Australia/Adelaide. Defaults to UTC in the container."
          },
          {
            "name": "PIHOLE_READ_ONLY",
            "format": "boolean",
            "default": "false",
            "description": "Expose only inspection tools. Every tool that can change Pi-hole is hidden and rejected if called."
          },
          {
            "name": "PIHOLE_TLS_SKIP_VERIFY",
            "format": "boolean",
            "default": "false",
            "description": "Set to true only for a Pi-hole serving a self-signed HTTPS certificate. A trusted certificate is the better fix."
          },
          {
            "name": "PIHOLE_REQUEST_TIMEOUT",
            "format": "string",
            "default": "30s",
            "description": "HTTP request timeout as a Go duration, e.g. 30s or 1m"
          },
          {
            "name": "PIHOLE_MAX_RETRIES",
            "format": "number",
            "default": "3",
            "description": "Retries after a transient Pi-hole API failure; 0 disables retrying"
          },
          {
            "name": "PIHOLE_RETRY_MAX_DELAY",
            "format": "string",
            "default": "8s",
            "description": "Upper bound on a single exponential-backoff wait, as a Go duration"
          }
        ]
      }
    ],
    "repository": {
      "id": "1202418772",
      "url": "https://github.com/hexamatic/pihole-mcp",
      "source": "github"
    },
    "websiteUrl": "https://github.com/hexamatic/pihole-mcp",
    "description": "Manage Pi-hole v6: DNS blocking, domains, clients, query analysis, DHCP, and multi-instance sync."
  }
}

Report an issue with this listing