How to integrate Nextdns MCP with Mastra AI

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Nextdns Logo
Mastra AI Logo
divider

Introduction

This guide walks you through connecting Nextdns to Mastra AI using the Composio tool router. By the end, you'll have a working Nextdns agent that can block access to adult websites for a profile, download dns logs from last week, show top domains queried by my devices, clear all dns logs for my home profile through natural language commands.

This guide will help you understand how to give your Mastra AI agent real control over a Nextdns account through Composio's Nextdns MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

TL;DR

Here's what you'll learn:
  • Set up your environment so Mastra, OpenAI, and Composio work together
  • Create a Tool Router session in Composio that exposes Nextdns tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Nextdns tool definitions and attach them as a toolset
  • Build a Mastra agent that can reason, call tools, and return structured results
  • Run an interactive CLI where you can chat with your Nextdns agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

  • MCP Client: Built-in support for Model Context Protocol servers
  • Toolsets: Organize tools into logical groups
  • Step Callbacks: Monitor and debug agent execution
  • OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

What is the Nextdns MCP server, and what's possible with it?

The Nextdns MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Nextdns account. It provides structured and secure access to your DNS security and privacy controls, so your agent can perform actions like blocking domains, managing profiles, analyzing DNS analytics, and clearing logs on your behalf.

  • Dynamic domain and TLD blocking: Instantly add domains or top-level domains to your denylist or security blocklist, helping you stay ahead of new threats.
  • Profile management and configuration: Create, update, or delete NextDNS configuration profiles to tailor DNS filtering and security settings for different users or devices.
  • Comprehensive DNS analytics: Retrieve detailed analytics by device, domain, or client IP to monitor DNS activity, spot anomalies, and optimize security policies.
  • Log management and export: Download DNS query logs for audit or troubleshooting, or clear logs entirely to maintain your privacy.
  • Control over block page settings: Enable or disable the block page for any configuration, giving you flexibility over how blocks are displayed to users.

Supported Tools & Triggers

Tools
Add Blocked TLDTool to add a top-level domain to the security blocklist for a nextdns profile.
Add Denylist DomainTool to add a domain to the denylist of a nextdns profile.
Toggle Block PageTool to enable or disable block page for a configuration.
Clear LogsTool to clear dns logs for a nextdns profile.
Create ProfileThis tool allows users to create a new nextdns profile.
Delete NextDNS ConfigurationTool to delete a nextdns configuration profile.
Download LogsTool to download dns logs for a profile.
Get Analytics DevicesTool to retrieve analytics aggregated by devices.
Get Analytics DomainsTool to retrieve analytics data for domains within a specific profile.
Get Analytics IPsTool to retrieve analytics aggregated by client ip addresses.
Get Analytics IP VersionsTool to retrieve analytics grouped by ip version within a specific profile.
Get Analytics Query TypesTool to retrieve dns query counts broken down by query type.
Get Analytics ReasonsTool to retrieve dns query counts broken down by classification reason.
Get Analytics StatusTool to retrieve analytics status for a specific profile.
Get LogsTool to retrieve logs for a specific nextdns profile with optional filters.
Get Profile DetailsRetrieves the details of a specific nextdns profile.
Get Setup InfoTool to get setup information for a provided configuration (profile).
List ConfigurationsTool to list all configurations (profiles) available on the nextdns account.
List Denylist DomainsTool to list domains in the denylist for a profile.
List Security SettingsTool to list current security options for a nextdns configuration.
List SettingsTool to list settings for a nextdns profile.
Log Client IPsTool to enable or disable logging of client ips for a nextdns configuration.
Toggle Domain LoggingTool to enable or disable logging of domains for a nextdns profile.
NextDNS LoginTool to authenticate to the nextdns api.
Get Monthly QueriesTool to get the number of dns queries made in the current month for a profile.
Remove Blocked TLDTool to remove a top-level domain from the security blocklist for a nextdns profile.
Remove Denylist DomainTool to remove a domain from a profile's denylist.
Rename ConfigurationTool to rename a nextdns configuration (profile).
Set AI Threat DetectionTool to enable or disable ai threat detection for a nextdns configuration.
Toggle Cryptojacking ProtectionTool to enable or disable cryptojacking protection for a nextdns configuration.
Set CSAM BlockingTool to enable or disable blocking of child sexual abuse material domains for a nextdns profile.
Toggle DGA ProtectionTool to enable or disable dga (domain generation algorithm) protection for a nextdns configuration.
Set DNS Rebinding ProtectionTool to enable or disable dns rebinding protection for a nextdns configuration.
Set Homograph ProtectionTool to enable or disable homograph attack protection for a nextdns configuration.
Set Newly Registered DomainsTool to enable or disable blocking of newly registered domains for a nextdns profile.
Toggle Parked Domains BlockingTool to enable or disable blocking of parked domains for a nextdns configuration.
Set Safe BrowsingTool to enable or disable google safe browsing for a nextdns configuration.
Toggle Threat Intelligence FeedsTool to enable or disable real-time threat intelligence feeds for a nextdns configuration.
Toggle Typosquatting ProtectionTool to enable or disable typosquatting protection for a nextdns configuration.
Update linked IPTool to update the linked ip for a nextdns profile.
Update Performance SettingsTool to update performance settings of a nextdns profile.
Update Privacy SettingsTool to update privacy settings for a profile.
Update ProfileTool to update an existing profile.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Node.js 18 or higher
  • A Composio account with an active API key
  • An OpenAI API key
  • Basic familiarity with TypeScript

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key.
  • You need credits or a connected billing setup to use the models.
  • Store the key somewhere safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Go to Settings and copy your API key.
  • This key lets your Mastra agent talk to Composio and reach Nextdns through MCP.

Install dependencies

bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

  • @composio/core is the Composio SDK for creating MCP sessions
  • @mastra/core provides the Agent class
  • @mastra/mcp is Mastra's MCP client
  • @ai-sdk/openai is the model wrapper for OpenAI
  • dotenv loads environment variables from .env

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio
  • COMPOSIO_USER_ID tells Composio which user this session belongs to
  • OPENAI_API_KEY lets the Mastra agent call OpenAI models

Import libraries and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
What's happening:
  • dotenv/config auto loads your .env so process.env.* is available
  • openai gives you a Mastra compatible model wrapper
  • Agent is the Mastra agent that will call tools and produce answers
  • MCPClient connects Mastra to your Composio MCP server
  • Composio is used to create a Tool Router session

Create a Tool Router session for Nextdns

typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["nextdns"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Nextdns MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "nextdns" for Nextdns access
  • session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
What's happening:
  • MCPClient takes an id for this client and a list of MCP servers
  • The headers property includes the x-api-key for authentication
  • getTools fetches the tool definitions exposed by the Nextdns toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "nextdns-mastra-agent",
    instructions: "You are an AI agent with Nextdns tools via Composio.",
    model: "openai/gpt-5",
  });
What's happening:
  • Agent is the core Mastra agent
  • name is just an identifier for logging and debugging
  • instructions guide the agent to use tools instead of only answering in natural language
  • model uses openai("gpt-5") to configure the underlying LLM

Set up interactive chat interface

typescript
let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\n");

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        nextdns: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • messages keeps the full conversation history in Mastra's expected format
  • agent.generate runs the agent with conversation history and Nextdns toolsets
  • maxSteps limits how many tool calls the agent can take in a single run
  • onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

Here's the complete code to get you started with Nextdns and Mastra AI:

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["nextdns"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nextdns: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "nextdns-mastra-agent",
    instructions: "You are an AI agent with Nextdns tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { nextdns: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Nextdns through Composio's Tool Router. You can extend this further by:
  • Adding other toolkits like Gmail, Slack, or GitHub
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows

How to build Nextdns MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Nextdns MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Nextdns MCP with Claude Agent SDK

Google ADK

Google ADK

Use Nextdns MCP with Google ADK

LangChain

LangChain

Use Nextdns MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Nextdns MCP with Vercel AI SDK

LlamaIndex

LlamaIndex

Use Nextdns MCP with LlamaIndex

CrewAI

CrewAI

Use Nextdns MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Nextdns MCP?

With a standalone Nextdns MCP server, the agents and LLMs can only access a fixed set of Nextdns tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Nextdns and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Mastra AI?

Yes, you can. Mastra AI fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Nextdns tools.

Can I manage the permissions and scopes for Nextdns while using Tool Router?

Yes, absolutely. You can configure which Nextdns scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Nextdns data and credentials are handled as safely as possible.

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free