AdGuard Home FAQs

Question 1

How can I deploy and integrate AdGuard Home MCP?

Accepted Answer

You can quickly run it via `npx` or deploy it as a Docker container (supporting `linux/amd64` and `linux/arm64`). It supports both `stdio` and `http` transports for flexible integration with your preferred AI environment, including direct configuration for Claude Code or Cursor.

Question 2

Can I limit the tools exposed to my AI assistant?

Accepted Answer

Absolutely. You can use environment variables to configure an 'access tier' (e.g., `read-only`) or specify a comma-separated list of 'categories' to expose only the necessary tools, keeping your AI's context clean and focused.

Question 3

What is AdGuard Home MCP?

Accepted Answer

AdGuard Home MCP is a Model Context Protocol server that exposes the complete AdGuard Home REST API as intuitive tools for AI assistants, enabling you to manage your DNS filtering and network settings using natural language commands.

Question 4

How does this tool enable AI management of AdGuard Home?

Accepted Answer

It provides 65 specialized tools across 16 API categories, allowing AI assistants like Claude Code, Claude Desktop, and Cursor to perform tasks such as managing DNS filtering rules, clients, DHCP settings, and more simply by understanding your natural language requests.

Question 5

Are there safety features for AI-driven AdGuard Home management?

Accepted Answer

Yes, AdGuard Home MCP includes crucial safety features. You can enable a 'read-only' mode for safe monitoring and use a 'destructive operation guard' that requires explicit confirmation for any critical or data-changing actions.

AdGuard Home

AdGuard Home

Key Features

Use Cases

Key Features

Use Cases