4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
AdGuard Home MCP Server

Bring Dns Filtering
to CrewAI

Learn how to connect AdGuard Home to CrewAI and start using 23 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Add ClientAdd Filter UrlAdd RewriteAdd Static LeaseCheck HostConfigure TlsGet Dhcp StatusGet Dns InfoGet Filtering StatusGet Query LogGet Query Log ConfigGet StatsGet StatusGet Tls StatusList Blocked ServicesList ClientsList RewritesSearch ClientsSet Dns ConfigSet ProtectionSet User RulesUpdate Blocked ServicesUpdate Query Log Config

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
AdGuard Home

What is the AdGuard Home MCP Server?

Connect your AdGuard Home instance to any AI agent and take full control of your network-wide privacy and security through natural conversation.

What you can do

  • Server Status — Monitor server health, active ports, protection states, and version information in real-time.
  • Protection Control — Toggle global filtering, safe browsing, and parental controls on or off, with optional timed durations.
  • DNS Configuration — View and update upstream DNS servers, bootstrap settings, and cache parameters (TTL, size, and optimistic caching).
  • Filter Management — Add new blocklist or allowlist URLs and manage custom user-defined filtering rules.
  • Client Insights — List and search for persistent or runtime clients, and configure specific security settings for individual devices.
  • Host Auditing — Instantly check if a specific domain is being filtered or blocked for a particular client.

How it works

  1. Subscribe to this server
  2. Enter your AdGuard Home Base URL and credentials (Username/Password)
  3. Start managing your network security from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Home Lab Enthusiasts — monitor and tweak your network-wide ad blocker without opening the web dashboard.
  • Network Administrators — quickly update upstream DNS providers or check why a specific host is being blocked.
  • Privacy-focused Users — manage custom filtering rules and client-specific protections through simple voice or text commands.

Built-in capabilities (23)

add_client

Add a new client

add_filter_url

Add a new filter URL

add_rewrite

Add a DNS rewrite

add_static_lease

Add a DHCP static lease

check_host

Check if a host is filtered

configure_tls

Configure TLS settings

get_dhcp_status

Get DHCP server status

get_dns_info

Get DNS configuration info

get_filtering_status

Get filtering status and lists

get_query_log

Get DNS query log

get_query_log_config

Get query log configuration

get_stats

Get DNS query statistics

get_status

Get AdGuard Home server status

get_tls_status

Get TLS configuration status

list_blocked_services

List all available blocked services

list_clients

List all clients

list_rewrites

List DNS rewrites

search_clients

Search for clients

set_dns_config

Update DNS settings

set_protection

globally. Enable or disable protection globally

set_user_rules

Set custom user filtering rules

update_blocked_services

Update blocked services schedule

update_query_log_config

Update query log configuration

Why CrewAI?

When paired with CrewAI, AdGuard Home becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call AdGuard Home tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

AdGuard Home in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

AdGuard Home and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect AdGuard Home to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for AdGuard Home in CrewAI

The AdGuard Home MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 23 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

AdGuard Home
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures AdGuard Home for CrewAI

Every tool call from CrewAI to the AdGuard Home MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I check if a specific website is being blocked for a specific client?

Yes, use the check_host tool. Provide the domain name and optionally the client IP to see if it's filtered and which rule is responsible.

02

Is it possible to pause the ad-blocking globally for a short period?

Yes. The set_protection tool allows you to disable filtering globally. You can also specify a duration in milliseconds if you want it to re-enable automatically.

03

How do I add a new blocklist URL using the AI?

Simply use the add_filter_url action. You'll need to provide a name for the filter, the URL of the list, and specify if it's a whitelist or blocklist.

04

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →