Mcp Pihole
Let your agent adjust Pi-hole v6 DNS blocking, lists, and stats on your homelab or edge network from natural language.
Overview
mcp-pihole is an MCP server for the Operate phase that manages Pi-hole v6 DNS blocking, statistics, and whitelist/blacklist rules through the web API.
What is this MCP server?
- Pi-hole v6 web API via stdio MCP (npm mcp-pihole-server v1.0.1)
- Manage whitelists, blacklists, and blocking stats
- Auth with PIHOLE_URL and PIHOLE_PASSWORD app password
- Suited for homelab and self-hosted network stacks
- Repository: aplaceforallmystuff/mcp-pihole
- Targets Pi-hole v6
- Package version 1.0.1 (mcp-pihole-server)
- 2 required configuration values: PIHOLE_URL, PIHOLE_PASSWORD
What problem does it solve?
Pi-hole changes usually mean logging into the web UI while debugging network or privacy issues mid-session.
Who is it for?
Self-hosters and indie ops folks who run Pi-hole v6 and want agent-driven DNS policy tweaks.
Skip if: Teams on managed corporate DNS with no Pi-hole instance or builders who never touch network infra.
What do I get? / Deliverables
Your agent can read Pi-hole stats and update lists via MCP once URL and app password are configured.
- Agent tools for Pi-hole stats and list management
- Documented env: PIHOLE_URL and PIHOLE_PASSWORD
- Faster DNS policy changes during ops work
Recommended MCP Servers
Journey fit
How it compares
Homelab DNS MCP integration, not a Pi-hole installer or security audit skill.
Common Questions / FAQ
Who is mcp-pihole for?
Solo builders and homelab operators who run Pi-hole v6 and want Claude Code or Cursor to manage blocking lists and stats.
When should I use mcp-pihole?
Use it in Operate when you need quick whitelist/blacklist updates, blocking insights, or DNS policy fixes without the Pi-hole dashboard.
How do I add mcp-pihole to my agent?
Install mcp-pihole-server from npm, set PIHOLE_URL (e.g. http://pihole.local:8080) and PIHOLE_PASSWORD, then register the stdio MCP server in your agent config.