Nextdns with Claude Agent SDK

How to integrate Nextdns MCP with Claude Agent SDK

Trusted by

GET STARTED FOR FREE GET A DEMO

30 min · no commitment · see it on your stack

Introduction Also integrate Nextdns with TL;DR What is Claude Agent SDK What is the Nextdns MCP server Supported Tools & Triggers Creating MCP Server - Stand-alone vs Composio SDK Step-by-step Guide Complete Code Conclusion How to build Nextdns MCP Agent with another framework Explore Other Toolkits FAQ

Connect Nextdns without Auth hassles

We manage OAuth, API Key, token refresh, and scopes, you just build.

Try for Free

Introduction

This guide walks you through connecting Nextdns to the Claude Agent SDK 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 your devices through natural language commands.

This guide will help you understand how to give your Claude Agent SDK 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.

Also integrate Nextdns with

OpenAI Agents SDK Claude Code Claude Cowork Codex OpenClaw Hermes CLI Google ADK LangChain Vercel AI SDK Mastra AI LlamaIndex CrewAI

TL;DR

Here's what you'll learn:

Get and set up your Claude/Anthropic and Composio API keys
Install the necessary dependencies
Initialize Composio and create a Tool Router session for Nextdns
Configure an AI agent that can use Nextdns as a tool
Run a live chat session where you can ask the agent to perform Nextdns operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

Native MCP Support: Built-in support for Model Context Protocol servers
Permission Modes: Control tool execution permissions
Streaming Responses: Real-time response streaming for interactive applications
Context Manager: Clean async context management for sessions

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 Allowlist EntryTool to add a domain to the allowlist of a NextDNS profile.

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.

Add Parental Control CategoryTool to add a content category to the parental control categories list.

Add Parental Control ServiceTool to add a service to the parental control services list of a NextDNS profile.

Add Privacy BlocklistTool to add a blocklist to the privacy blocklists for a NextDNS profile.

Add Privacy Native TrackerTool to add a native tracking service to the blocked list for a NextDNS profile.

Add DNS Rewrite RuleTool to add a DNS rewrite rule to a NextDNS profile.

Clear LogsTool to clear DNS logs for a NextDNS profile.

Create ProfileThis tool allows users to create a new NextDNS profile.

Delete Allowlist EntryTool to remove a domain from a NextDNS profile's allowlist.

Delete NextDNS ConfigurationTool to delete a NextDNS configuration profile.

Delete Parental Control CategoryTool to remove a category from parental control blocked categories.

Delete Parental Control ServiceTool to remove a service from parental control blocked services.

Delete Privacy BlocklistTool to remove a blocklist from the privacy blocklists for a NextDNS profile.

Delete Privacy Native TrackerTool to remove a native tracking entry from a NextDNS profile's privacy settings.

Delete DNS Rewrite RuleTool to delete a DNS rewrite rule from a NextDNS profile.

Download LogsRetrieves the download URL for exported DNS query logs from a NextDNS profile.

Get AllowlistTool to retrieve the list of allowed domains for a NextDNS profile.

Get Analytics DestinationsTool to retrieve destination analytics for a profile showing query destinations by country or GAFAM company.

Get Analytics DevicesTool to retrieve device analytics for a profile showing identified devices with names, models, and query counts.

Get Analytics DNSSECTool to retrieve DNSSEC validation analytics for a profile showing validated vs non-validated query counts.

Get Analytics DomainsTool to retrieve analytics data for domains within a specific profile.

Get Analytics EncryptionTool to retrieve encryption analytics for a profile showing encrypted vs unencrypted query counts.

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 ProtocolsTool to retrieve protocol analytics for a specific profile showing DNS protocol distribution (DNS-over-HTTPS, DNS-over-TLS, UDP).

Get Analytics Query TypesTool to retrieve DNS query counts broken down by query type.

Get Analytics Blocking ReasonsTool to retrieve blocking reasons analytics showing blocklists, native tracking protection, and other reasons for blocked queries.

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 Parental Control SettingsTool to get parental control settings for a profile.

Get Parental Control CategoriesTool to get the list of blocked/allowed content categories for parental control.

Get Parental Control ServicesTool to get the list of blocked/allowed services for parental control.

Get Performance SettingsTool to get performance settings for a profile including ECS, cache boost, and CNAME flattening configuration.

Get Privacy SettingsTool to get privacy settings for a profile including blocklists, native tracking settings, disguised trackers, and affiliate settings.

Get Profile DetailsRetrieves the details of a specific NextDNS profile.

Get DNS RewritesTool to retrieve the list of DNS rewrites for a NextDNS profile.

Get Security TLDsTool to get the list of blocked TLDs (top-level domains) for a profile's security settings.

Get Profile SettingsTool to get all settings for a NextDNS profile including logs, block page, performance, and web3 settings.

Get Block Page SettingsTool to retrieve the block page settings for a NextDNS profile.

Get Logging SettingsTool to retrieve the logging settings for a NextDNS profile.

List Denylist DomainsTool to list domains in the denylist for a profile.

List ProfilesList all NextDNS profiles for the authenticated user, returning profile IDs and configurations.

List Security SettingsTool to list current security options for a NextDNS configuration.

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.

Remove Blocked TLDTool to remove a top-level domain from the security blocklist for a NextDNS profile.

Remove Denylist DomainRemoves a domain from a NextDNS profile's denylist (blocklist).

Rename ConfigurationTool to rename a NextDNS configuration (profile).

Replace AllowlistTool to replace the entire allowlist for a NextDNS profile.

Replace DenylistTool to replace the entire denylist (blocked domains) for a NextDNS profile.

Replace Parental Control CategoriesTool to replace the entire list of blocked/allowed content categories for parental control.

Replace Parental Control ServicesTool to replace the entire list of blocked/allowed services for parental control.

Replace Privacy BlocklistsTool to replace the entire list of privacy blocklists for a NextDNS profile.

Replace Privacy Native Tracking ServicesTool to replace the entire list of blocked native tracking services for a NextDNS profile.

Replace Security TLDsTool to replace the entire list of blocked TLDs (top-level domains) for a NextDNS profile's security settings.

Update Allowlist EntryTool to update a specific allowlist entry in a NextDNS profile.

Update Denylist EntryUpdates a specific denylist entry in a NextDNS profile, typically to toggle its active status.

Update linked IPUpdates the linked IP address for a NextDNS profile to the current caller's public IP.

Update Parental Control SettingsTool to update parental control settings for a NextDNS profile.

Update Parental Control CategoryTool to update a specific category entry in parental control settings.

Update Parental Control ServiceTool to update a specific service entry in parental control settings.

Update Performance SettingsTool to update performance settings of a NextDNS profile.

Update Privacy SettingsTool to update privacy settings for a profile.

Update Security SettingsTool to update security settings for a profile.

Update SettingsTool to update settings for a NextDNS profile including logs, block page, performance, and web3 settings.

Update Block Page SettingsTool to update block page settings for a NextDNS profile.

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

What is Composio SDK?

Composio's Composio SDK 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 Composio SDK

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

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

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

Step-by-step Guide

Prerequisites

Before starting, make sure you have:

Composio API Key and Claude/Anthropic API Key
Primary know-how of Claude Agents SDK
A Nextdns account
Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key

Go to the Anthropic Console and create an API key. You'll need credits to use the models.
Keep the API key safe.

Composio API Key

Log in to the Composio dashboard.
Navigate to your API settings and generate a new API key.
Store this key securely as you'll need it for authentication.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

composio-anthropic provides Composio integration for Anthropic
claude-agent-sdk is the core agent framework
python-dotenv loads environment variables

Set up environment variables

bash

COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

COMPOSIO_API_KEY authenticates with Composio
USER_ID identifies the user for session management
ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

What's happening:

We're importing all necessary libraries including the Claude Agent SDK and Composio
The load_dotenv() function loads environment variables from your .env file
This setup prepares the foundation for connecting Claude with Nextdns functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Nextdns
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["nextdns"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

What's happening:

The function checks for the required COMPOSIO_API_KEY environment variable
We're creating a Composio instance using our API key
The create method creates a Tool Router session for Nextdns
The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Nextdns tools via Composio.",
    max_turns=10
)

What's happening:

We're configuring the Claude Agent options with the MCP server URL
permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
The system prompt instructs the agent that it has access to Nextdns
max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()

What's happening:

The Claude SDK client is created using the async context manager pattern
The agent processes each query and streams the response back in real-time
The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

What's happening:

This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

Here's the complete code to get you started with Nextdns and Claude Agent SDK:

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Nextdns
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["nextdns"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Nextdns tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Nextdns through Composio's Tool Router.

Key features:

Native MCP support through Claude's agent framework
Streaming responses for real-time interaction
Permission bypass for smooth automated workflows

You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Nextdns MCP Agent with another framework

OpenAI Agents SDK

Use Nextdns MCP with OpenAI Agents SDK

Claude Code

Use Nextdns MCP with Claude Code

Claude Cowork

Use Nextdns MCP with Claude Cowork

Codex

Use Nextdns MCP with Codex

OpenClaw

Use Nextdns MCP with OpenClaw

Hermes

Use Nextdns MCP with Hermes

CLI

Use Nextdns MCP with CLI

Google ADK

Use Nextdns MCP with Google ADK

LangChain

Use Nextdns MCP with LangChain

Vercel AI SDK

Use Nextdns MCP with Vercel AI SDK

Mastra AI

Use Nextdns MCP with Mastra AI

LlamaIndex

Use Nextdns MCP with LlamaIndex

CrewAI

Use Nextdns MCP with CrewAI

Explore Other Toolkits

Excel

Oauth2S2s Oauth2

Microsoft Excel is a robust spreadsheet application for organizing, analyzing, and visualizing data. It's the go-to tool for calculations, reporting, and flexible data management.

21risk

Api Key

21RISK is a web app built for easy checklist, audit, and compliance management. It streamlines risk processes so teams can focus on what matters.

Abstract

Api Key

Abstract provides a suite of APIs for automating data validation and enrichment tasks. It helps developers streamline workflows and ensure data quality with minimal effort.

TOOLKIT MARKETPLACE

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 Claude Agent SDK?

Yes, you can. Claude Agent SDK 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

Never worry about agent reliability

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

Get started for free Get a demo↗

Harsha GaddipatiCo-founder, Slashy

Karan skipped his own birthday party to fix our critical issue. It was 10 pm and he diverted his Waymo to help us instead. This really sets the bar, shows you the commitment you need to have when users rely on your software.

Abhi AryaCo-founder, Opennote

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it has immensely helped in keeping new users on the platform.

Nirman DaveCEO, Zams

We chose Composio over Pipedream because it delivered depth where it mattered. It supported niche tools and tricky edge cases that other platforms simply ignored. Giving us confidence to scale without compromising.

Ryan YuFounder, Extra Thursday

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down in the complexities of managing agent auth would have been a death sentence for Extra Thursday.

Tomisin JenrolaFounder & CEO, SwarmZero

Before partnering with Composio, adding tool integrations was a slow, resource-intensive process. Each integration could take weeks or months of engineering time, and maintaining them meant constantly keeping up with API changes.

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

How to integrate Nextdns MCP with Claude Agent SDK

Table of Contents

Connect Nextdns without Auth hassles

Introduction

Also integrate Nextdns with

TL;DR

What is Claude Agent SDK?

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

Supported Tools & Triggers

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

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for Claude/Anthropic and Composio

Install dependencies

Set up environment variables

Import dependencies

Create a Composio instance and Tool Router session

Configure Claude Agent with MCP

Create client and start chat loop

Run the application

Complete Code

Conclusion

How to build Nextdns MCP Agent with another framework

OpenAI Agents SDK

Claude Code

Claude Cowork

Codex

OpenClaw

Hermes

CLI

Google ADK

LangChain

Vercel AI SDK

Mastra AI

LlamaIndex

CrewAI

Explore Other Toolkits

Excel

21risk

Abstract

FAQ

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

Can I use Tool Router MCP with Claude Agent SDK?

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

How safe is my data with Composio Tool Router?

Used by agents from

Never worry about agent reliability