Manage AdGuard Home through AI assistants
Connect Runs on your machine
claude mcp add mcp-adguard-home -e ADGUARD_URL=<ADGUARD_URL> -e ADGUARD_USERNAME=<ADGUARD_USERNAME> -e ADGUARD_PASSWORD=<ADGUARD_PASSWORD> -- npx -y @samik081/[email protected]{
"mcpServers": {
"mcp-adguard-home": {
"command": "npx",
"args": [
"-y",
"@samik081/[email protected]"
],
"env": {
"ADGUARD_URL": "<ADGUARD_URL>",
"ADGUARD_USERNAME": "<ADGUARD_USERNAME>",
"ADGUARD_PASSWORD": "<ADGUARD_PASSWORD>"
}
}
}
}{
"mcpServers": {
"mcp-adguard-home": {
"command": "npx",
"args": [
"-y",
"@samik081/[email protected]"
],
"env": {
"ADGUARD_URL": "<ADGUARD_URL>",
"ADGUARD_USERNAME": "<ADGUARD_USERNAME>",
"ADGUARD_PASSWORD": "<ADGUARD_PASSWORD>"
}
}
}
}{
"servers": {
"mcp-adguard-home": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@samik081/[email protected]"
],
"env": {
"ADGUARD_URL": "<ADGUARD_URL>",
"ADGUARD_USERNAME": "<ADGUARD_USERNAME>",
"ADGUARD_PASSWORD": "<ADGUARD_PASSWORD>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
ADGUARD_URLRequired | URL of the AdGuard Home instance (e.g. http://192.168.1.1:3000) |
ADGUARD_USERNAMEOptional, secret | AdGuard Home username (omit if authentication is disabled) |
ADGUARD_PASSWORDOptional, secret | AdGuard Home password (omit if authentication is disabled) |
Details
| Package | @samik081/[email protected] (NPM, stdio) |
| Package | ghcr.io/samik081/mcp-adguard-home:0.11.0 (OCI, stdio) |
| First published | 12 Nov 2026 |
| Last updated | 12 Nov 2026 |
| Registry name | io.github.Samik081/mcp-adguard-home |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.