member badge
Kate Trojanowski
Getting an answer out of DNSFilter has always meant knowing where to look — which report, which filter, which date range. For admins who live in the dashboard that's muscle memory. For everyone else, and for anyone trying to line DNSFilter up against the rest of their security stack, it's friction that adds up.
The DNSFilter MCP Server removes the dashboard from between the question and the answer. Connect an AI assistant through the Model Context Protocol and ask in plain language: what got blocked and why, what a device has been doing, which Roaming Clients have gone quiet. Make the policy change or the block list update in the same conversation, with confirmation before anything is written.
Because MCP is an open standard, DNSFilter data can be correlated with every other tool that speaks it — endpoint, asset management, ITSM — in a single investigation rather than five browser tabs.
What This Means for You
  • Ask for reporting in plain language instead of rebuilding the same view every week
  • Work a blocked-domain ticket end to end without leaving the assistant
  • Correlate DNSFilter with other MCP-connected tools in one investigation
  • Make policy and list changes conversationally, with a confirmation step before each write
  • Access follows the signed-in admin's own permissions — the assistant sees exactly what that person can see
Find it under Integrations → AI Connectors. Available on Core, Plus, and Enterprise.