| name | pp-adguard-home | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| description | Printing Press CLI for Adguard Home. AdGuard Home REST-ish API. Our admin web interface is built on top of this REST-ish API. | |||||||||||||||||
| author | Eric Jung | |||||||||||||||||
| license | Apache-2.0 | |||||||||||||||||
| argument-hint | <command> [args] | install cli|mcp | |||||||||||||||||
| allowed-tools | Read Bash | |||||||||||||||||
| metadata |
|
This skill drives the adguard-home-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:
- Install via the Printing Press installer. It defaults binaries to
$HOME/.local/binon macOS/Linux and%LOCALAPPDATA%\Programs\PrintingPress\binon Windows:npx -y @mvanhorn/printing-press-library install adguard-home --cli-only
- Verify:
adguard-home-pp-cli --version - Ensure the reported install directory is on
$PATHfor the agent/runtime that will invoke this skill.
If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer):
go install github.com/mvanhorn/printing-press-library/library/monitoring/adguard-home/cmd/adguard-home-pp-cli@latestIf --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.
access — Manage access
adguard-home-pp-cli access list— List (dis)allowed clients, blocked hosts, etc.adguard-home-pp-cli access set— Set (dis)allowed clients, blocked hosts, etc.
adguard-home-profile — Manage adguard home profile
adguard-home-pp-cli adguard-home-profile get— Getadguard-home-pp-cli adguard-home-profile update— Updates current user info
apple — Manage apple
adguard-home-pp-cli apple mobile-config-do-h— Get DNS over HTTPS .mobileconfig.adguard-home-pp-cli apple mobile-config-do-t— Get DNS over TLS .mobileconfig.
blocked-services — Blocked services controls
adguard-home-pp-cli blocked-services all— Get available services to use for blockingadguard-home-pp-cli blocked-services available-services— Deprecated: UseGET /blocked_services/allinstead.adguard-home-pp-cli blocked-services list— Deprecated: UseGET /blocked_services/getinstead.adguard-home-pp-cli blocked-services schedule— Get blocked servicesadguard-home-pp-cli blocked-services schedule-update— Update blocked servicesadguard-home-pp-cli blocked-services set— Deprecated: UsePUT /blocked_services/updateinstead.
cache-clear — Manage cache clear
adguard-home-pp-cli cache-clear— Clear DNS cache
clients — Clients list operations
adguard-home-pp-cli clients add— Add a new clientadguard-home-pp-cli clients delete— Remove a clientadguard-home-pp-cli clients find— Get information about clients by their IP addresses or ClientIDs.adguard-home-pp-cli clients search— Retrieve information about clients by performing an exact match search using IP addresses, CIDRs, MAC addresses, or...adguard-home-pp-cli clients status— Get information about configured clientsadguard-home-pp-cli clients update— Update client information
dhcp — Built-in DHCP server controls
adguard-home-pp-cli dhcp add-static-lease— Adds a static leaseadguard-home-pp-cli dhcp check-active— Searches for an active DHCP server on the networkadguard-home-pp-cli dhcp interfaces— Gets the available interfacesadguard-home-pp-cli dhcp remove-static-lease— Removes a static leaseadguard-home-pp-cli dhcp reset— Reset DHCP configurationadguard-home-pp-cli dhcp reset-leases— Reset DHCP leasesadguard-home-pp-cli dhcp set-config— Updates the current DHCP server configurationadguard-home-pp-cli dhcp status— Gets the current DHCP settings and statusadguard-home-pp-cli dhcp update-static-lease— Updates IP address, hostname of the static lease. IP version must be the same as previous.
dns-config — Manage dns config
adguard-home-pp-cli dns-config— Set general DNS parameters
dns-info — Manage dns info
adguard-home-pp-cli dns-info— Get general DNS parameters
filtering — Rule-based filtering
adguard-home-pp-cli filtering add-url— Add filter URL or an absolute file pathadguard-home-pp-cli filtering check-host— Check if host name is filteredadguard-home-pp-cli filtering config— Set filtering parametersadguard-home-pp-cli filtering refresh— Reload filtering rules from URLs. This might be needed if new URL was just added and you don't want to wait for...adguard-home-pp-cli filtering remove-url— Remove filter URLadguard-home-pp-cli filtering set-rules— Set user-defined filter rulesadguard-home-pp-cli filtering set-url— Set URL parametersadguard-home-pp-cli filtering status— Get filtering parameters
i18n — Application localization
adguard-home-pp-cli i18n change-language— Change current language. Argument must be an ISO 639-1 two-letter code.adguard-home-pp-cli i18n current-language— Get currently set language. Result is ISO 639-1 two-letter code. Empty result means default language.
install — First-time install configuration handlers
adguard-home-pp-cli install check-config— Checks configurationadguard-home-pp-cli install configure— Applies the initial configuration.adguard-home-pp-cli install get-addresses— Gets the network interfaces information.
login — Manage login
adguard-home-pp-cli login— Perform administrator log-in
logout — Manage logout
adguard-home-pp-cli logout— Perform administrator log-out
parental — Blocking adult and explicit materials
adguard-home-pp-cli parental disable— Disable parental filteringadguard-home-pp-cli parental enable— Enable parental filteringadguard-home-pp-cli parental status— Get parental filtering status
protection — Manage protection
adguard-home-pp-cli protection— Set protection state and duration
querylog — Manage querylog
adguard-home-pp-cli querylog get-query-log-config— Get query log parametersadguard-home-pp-cli querylog put-query-log-config— Set query log parametersadguard-home-pp-cli querylog query-log— Get DNS server query log.
querylog-clear — Manage querylog clear
adguard-home-pp-cli querylog-clear— Clear query log
querylog-config — Manage querylog config
adguard-home-pp-cli querylog-config— Deprecated: UsePUT /querylog/config/updateinstead.
querylog-info — Manage querylog info
adguard-home-pp-cli querylog-info— Deprecated: UseGET /querylog/configinstead. NOTE: Ifintervalwas configured by editing configuration file or...
rewrite — DNS rewrites
adguard-home-pp-cli rewrite add— Add a new Rewrite ruleadguard-home-pp-cli rewrite delete— Remove a Rewrite ruleadguard-home-pp-cli rewrite list— Get list of Rewrite rulesadguard-home-pp-cli rewrite settings-get— Get rewrite settingsadguard-home-pp-cli rewrite settings-update— Update rewrite settingsadguard-home-pp-cli rewrite update— Update a Rewrite rule
safebrowsing — Blocking malware/phishing sites
adguard-home-pp-cli safebrowsing disable— Disable safebrowsingadguard-home-pp-cli safebrowsing enable— Enable safebrowsingadguard-home-pp-cli safebrowsing status— Get safebrowsing status
safesearch — Enforce family-friendly results in search engines
adguard-home-pp-cli safesearch disable— Disable safesearchadguard-home-pp-cli safesearch enable— Enable safesearchadguard-home-pp-cli safesearch settings— Update safesearch settingsadguard-home-pp-cli safesearch status— Get safesearch status
stats — AdGuard Home statistics
adguard-home-pp-cli stats get-config— Get statistics parametersadguard-home-pp-cli stats put-config— Set statistics parametersadguard-home-pp-cli stats stats— Get DNS server statistics
stats-config — Manage stats config
adguard-home-pp-cli stats-config— Deprecated: UsePUT /stats/config/updateinstead.
stats-info — Manage stats info
adguard-home-pp-cli stats-info— Deprecated: UseGET /stats/configinstead. NOTE: Ifintervalwas configured by editing configuration file or new...
stats-reset — Manage stats reset
adguard-home-pp-cli stats-reset— Reset all statistics to zeroes
status — Manage status
adguard-home-pp-cli status— Get DNS server current status and general settings
test-upstream-dns — Manage test upstream dns
adguard-home-pp-cli test-upstream-dns— Test upstream configuration
tls — AdGuard Home HTTPS/DoH/DoQ/DoT settings
adguard-home-pp-cli tls configure— Updates current TLS configurationadguard-home-pp-cli tls status— Returns TLS configuration and its statusadguard-home-pp-cli tls validate— Checks if the current TLS configuration is valid
update — Manage update
adguard-home-pp-cli update— Begin auto-upgrade procedure
version-json — Manage version json
adguard-home-pp-cli version-json— Gets information about the latest available version of AdGuard
When you know what you want to do but not which command does it, ask the CLI directly:
adguard-home-pp-cli which "<capability in your own words>"which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query.
Run adguard-home-pp-cli auth setup to print the URL and steps for getting a key (add --launch to open the URL). Then set:
export ADGUARD_HOME_USERNAME="<your-key>"Or persist it in ~/.config/adguard-home-pp-cli/config.toml.
Run adguard-home-pp-cli doctor to verify setup.
Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.
-
Pipeable — JSON on stdout, errors on stderr
-
Filterable —
--selectkeeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:adguard-home-pp-cli access list --agent --select id,name,status
-
Previewable —
--dry-runshows the request without sending -
Offline-friendly — sync/search commands can use the local SQLite store when available
-
Non-interactive — never prompts, every input is a flag
-
Explicit retries — use
--idempotentonly when an already-existing create should count as success
Commands that read from the local store or the API wrap output in a provenance envelope:
{
"meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
"results": <data>
}Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal AND no machine-format flag (--json, --csv, --compact, --quiet, --plain, --select) is set — piped/agent consumers and explicit-format runs get pure JSON on stdout.
When you (or the agent) notice something off about this CLI, record it:
adguard-home-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
adguard-home-pp-cli feedback --stdin < notes.txt
adguard-home-pp-cli feedback list --json --limit 10
Entries are stored locally at ~/.adguard-home-pp-cli/feedback.jsonl. They are never POSTed unless ADGUARD_HOME_FEEDBACK_ENDPOINT is set AND either --send is passed or ADGUARD_HOME_FEEDBACK_AUTO_SEND=true. Default behavior is local-only.
Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.
Every command accepts --deliver <sink>. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:
| Sink | Effect |
|---|---|
stdout |
Default; write to stdout only |
file:<path> |
Atomically write output to <path> (tmp + rename) |
webhook:<url> |
POST the output body to the URL (application/json or application/x-ndjson when --compact) |
Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.
A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.
adguard-home-pp-cli profile save briefing --json
adguard-home-pp-cli --profile briefing access list
adguard-home-pp-cli profile list --json
adguard-home-pp-cli profile show briefing
adguard-home-pp-cli profile delete briefing --yes
Explicit flags always win over profile values; profile values win over defaults. agent-context lists all available profiles under available_profiles so introspecting agents discover them at runtime.
| Code | Meaning |
|---|---|
| 0 | Success |
| 2 | Usage error (wrong arguments) |
| 3 | Resource not found |
| 4 | Authentication required |
| 5 | API error (upstream issue) |
| 7 | Rate limited (wait and retry) |
| 10 | Config error |
Parse $ARGUMENTS:
- Empty,
help, or--help→ showadguard-home-pp-cli --helpoutput - Starts with
install→ ends withmcp→ MCP installation; otherwise → see Prerequisites above - Anything else → Direct Use (execute as CLI command with
--agent)
- Install the MCP server:
go install github.com/mvanhorn/printing-press-library/library/monitoring/adguard-home/cmd/adguard-home-pp-mcp@latest
- Register with Claude Code:
claude mcp add adguard-home-pp-mcp -- adguard-home-pp-mcp
- Verify:
claude mcp list
- Check if installed:
which adguard-home-pp-cliIf not found, offer to install (see Prerequisites at the top of this skill). - Match the user query to the best command from the Unique Capabilities and Command Reference above.
- Execute with the
--agentflag:adguard-home-pp-cli <command> [subcommand] [args] --agent
- If ambiguous, drill into subcommand help:
adguard-home-pp-cli <command> --help.