Adguardhome Mcp

io.github.mrfentmenv1.0.0Updated Oct 1, 2026

Query your AdGuard Home: status, stats, query log. Endpoints per official docs.

VerifiedSTDIODesktop onlySecurity & MonitoringCloud & Infrastructure

Overview

AI-generated overview

Lets an assistant query an AdGuard Home instance for status, statistics, and query log data.

What it does
This server exposes AdGuard Home's API to an assistant, so it can read the instance's status, retrieve statistics, and pull query log entries. It is described as covering the endpoints from the official AdGuard Home documentation. It runs locally over stdio as an npm package.
When to use it
Useful when you already run AdGuard Home and want an assistant to check whether filtering is active, review traffic and blocked-query statistics, or inspect recent DNS query log entries without opening the web UI.
Requirements
Runs as a local process over stdio, installed from the npm package adguardhome-mcp, so Node.js and npm are needed. It must be able to reach your AdGuard Home instance. No authentication, environment variables, or headers are declared in the manifest.
Before you install
The manifest declares no authentication, so how the server reaches your AdGuard Home instance is not specified; AdGuard Home normally requires credentials, and any it uses should be treated as sensitive. Query log data can reveal browsing activity, so consider what is sent to the model. The description only mentions querying, but confirm whether any tool can change filtering or configuration before installing.

Installation

In SourceWeft

  1. Open Adguardhome Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.0LatestOct 1, 2026