# How to integrate Nextdns MCP with Claude Code

```json
{
  "title": "How to integrate Nextdns MCP with Claude Code",
  "toolkit": "Nextdns",
  "toolkit_slug": "nextdns",
  "framework": "Claude Code",
  "framework_slug": "claude-code",
  "url": "https://composio.dev/toolkits/nextdns/framework/claude-code",
  "markdown_url": "https://composio.dev/toolkits/nextdns/framework/claude-code.md",
  "updated_at": "2026-05-12T10:20:13.991Z"
}
```

## Introduction

Manage your Nextdns directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.
You can do this in two different ways:
- Via [Composio Connect](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code) - Direct and easiest approach
- Via [Composio SDK](https://docs.composio.dev/docs?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_sdk) - Programmatic approach with more control

## Also integrate Nextdns with

- [OpenAI Agents SDK](https://composio.dev/toolkits/nextdns/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/nextdns/framework/claude-agents-sdk)
- [Claude Cowork](https://composio.dev/toolkits/nextdns/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/nextdns/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/nextdns/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/nextdns/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/nextdns/framework/cli)
- [Google ADK](https://composio.dev/toolkits/nextdns/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/nextdns/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/nextdns/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/nextdns/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/nextdns/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/nextdns/framework/crew-ai)

## TL;DR

- Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
- Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
- Handling Large tool responses out of LLM context to minimize context rot.
- Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

## Connect Nextdns to Claude Code

### Connecting Nextdns to Claude Code using Composio
1. Add the Composio MCP to Claude

```bash
claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp
```

## What is Claude Code?

Claude Code is Anthropic's command line developer tool that lets you use Claude directly inside your terminal. Instead of switching between your editor, browser, and chat, you can stay in your project folder and ask Claude to help you build, debug, refactor, and understand code right where you're working.
Key features include:
- Terminal-Native Experience: Work with Claude directly in your command line without switching contexts
- MCP Support: Built-in support for Model Context Protocol servers to extend Claude's capabilities
- Project Context: Claude understands your project structure and can read, write, and modify files
- Interactive Development: Ask questions, debug code, and get help in real-time while coding
- Multi-Platform: Works on macOS, Linux, WSL, and Windows

## 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

| Tool slug | Name | Description |
|---|---|---|
| `NEXTDNS_ADD_ALLOWLIST_ENTRY` | Add Allowlist Entry | Tool to add a domain to the allowlist of a NextDNS profile. Use when allowing specific domains under a profile after obtaining its ID. |
| `NEXTDNS_ADD_BLOCKED_TLD` | Add Blocked TLD | Tool to add a top-level domain to the security blocklist for a NextDNS profile. Use after listing current security settings to ensure the TLD is not already blocked. |
| `NEXTDNS_ADD_DENYLIST_DOMAIN` | Add Denylist Domain | Tool to add a domain to the denylist of a NextDNS profile. Use when blocking specific domains under a profile after obtaining its ID. |
| `NEXTDNS_ADD_PARENTAL_CONTROL_CATEGORY` | Add Parental Control Category | Tool to add a content category to the parental control categories list. Use when you need to add a new category to block or allow specific content types like pornography, gambling, or social networks. |
| `NEXTDNS_ADD_PARENTAL_CONTROL_SERVICE` | Add Parental Control Service | Tool to add a service to the parental control services list of a NextDNS profile. Use when blocking specific services (like social media platforms) under a profile. |
| `NEXTDNS_ADD_PRIVACY_BLOCKLIST` | Add Privacy Blocklist | Tool to add a blocklist to the privacy blocklists for a NextDNS profile. Use when enabling additional privacy blocklists for a profile. |
| `NEXTDNS_ADD_PRIVACY_NATIVE` | Add Privacy Native Tracker | Tool to add a native tracking service to the blocked list for a NextDNS profile. Use when blocking native trackers from specific vendors. |
| `NEXTDNS_ADD_REWRITE` | Add DNS Rewrite Rule | Tool to add a DNS rewrite rule to a NextDNS profile. Use when you need to configure custom DNS resolution for specific domains. |
| `NEXTDNS_CLEAR_LOGS` | Clear Logs | Tool to clear DNS logs for a NextDNS profile. Use when you want to remove all existing query logs for a given profile. Note: this operation cannot be undone. |
| `NEXTDNS_CREATE_PROFILE` | Create Profile | This tool allows users to create a new NextDNS profile. It uses the POST method at the endpoint https://api.nextdns.io/profiles. A profile is a distinct configuration set for DNS filtering and security settings. |
| `NEXTDNS_DELETE_ALLOWLIST_ENTRY` | Delete Allowlist Entry | Tool to remove a domain from a NextDNS profile's allowlist. Use when you need to stop allowing a previously whitelisted domain. |
| `NEXTDNS_DELETE_CONFIG` | Delete NextDNS Configuration | Tool to delete a NextDNS configuration profile. Use when you need to remove an existing profile by its ID. Use after confirming the profile exists. |
| `NEXTDNS_DELETE_PARENTAL_CONTROL_CATEGORY` | Delete Parental Control Category | Tool to remove a category from parental control blocked categories. Use when you need to unblock a content category that was previously blocked. Use 'Get Parental Control Categories' first to verify the category is currently blocked. |
| `NEXTDNS_DELETE_PARENTAL_CONTROL_SERVICE` | Delete Parental Control Service | Tool to remove a service from parental control blocked services. Use when you need to unblock a service (like TikTok, Instagram, or other apps) that was previously blocked. |
| `NEXTDNS_DELETE_PRIVACY_BLOCKLIST` | Delete Privacy Blocklist | Tool to remove a blocklist from the privacy blocklists for a NextDNS profile. Use when disabling or removing privacy blocklists from a profile. |
| `NEXTDNS_DELETE_PRIVACY_NATIVE` | Delete Privacy Native Tracker | Tool to remove a native tracking entry from a NextDNS profile's privacy settings. Use when you need to stop blocking a specific native app tracker (like Apple, Samsung, Huawei, etc.). |
| `NEXTDNS_DELETE_REWRITE` | Delete DNS Rewrite Rule | Tool to delete a DNS rewrite rule from a NextDNS profile. Use when you need to remove an existing DNS rewrite rule by its ID. |
| `NEXTDNS_DOWNLOAD_LOGS` | Download Logs | Retrieves the download URL for exported DNS query logs from a NextDNS profile. Returns a time-limited URL pointing to a CSV file containing the profile's DNS logs. Use this to export log data for analysis, backup, or compliance purposes. The profile_id can be obtained from the list_configurations action. |
| `NEXTDNS_GET_ALLOWLIST` | Get Allowlist | Tool to retrieve the list of allowed domains for a NextDNS profile. Use when you need to view all domains currently whitelisted in a profile. |
| `NEXTDNS_GET_ANALYTICS_DESTINATIONS` | Get Analytics Destinations | Tool to retrieve destination analytics for a profile showing query destinations by country or GAFAM company. Use when you need to understand geographic distribution or big tech company query patterns. |
| `NEXTDNS_GET_ANALYTICS_DEVICES2` | Get Analytics Devices | Tool to retrieve device analytics for a profile showing identified devices with names, models, and query counts. Use when you need per-device query metrics within a specific time frame. |
| `NEXTDNS_GET_ANALYTICS_DNSSEC` | Get Analytics DNSSEC | Tool to retrieve DNSSEC validation analytics for a profile showing validated vs non-validated query counts. Use after selecting a profile to analyze DNSSEC validation statistics. |
| `NEXTDNS_GET_ANALYTICS_DOMAINS` | Get Analytics Domains | Tool to retrieve analytics data for domains within a specific profile. Use after confirming the profile ID to get per-domain query stats. |
| `NEXTDNS_GET_ANALYTICS_ENCRYPTION` | Get Analytics Encryption | Tool to retrieve encryption analytics for a profile showing encrypted vs unencrypted query counts. Use when you need to understand the breakdown of DNS queries by encryption status (DoH/DoT vs plain DNS). |
| `NEXTDNS_GET_ANALYTICS_IPS` | Get Analytics IPs | Tool to retrieve analytics aggregated by client IP addresses. Use when you need to analyze DNS query distribution per client IP for a given profile. |
| `NEXTDNS_GET_ANALYTICS_IP_VERSIONS` | Get Analytics IP Versions | Tool to retrieve analytics grouped by IP version within a specific profile. Use after you have a profile ID to see IPv4 vs IPv6 query counts. |
| `NEXTDNS_GET_ANALYTICS_PROTOCOLS` | Get Analytics Protocols | Tool to retrieve protocol analytics for a specific profile showing DNS protocol distribution (DNS-over-HTTPS, DNS-over-TLS, UDP). Use after confirming the profile ID to analyze protocol usage patterns. |
| `NEXTDNS_GET_ANALYTICS_QUERY_TYPES` | Get Analytics Query Types | Tool to retrieve DNS query counts broken down by query type. Use after selecting a profile and specifying date filters to analyze distribution by type. |
| `NEXTDNS_GET_ANALYTICS_REASONS2` | Get Analytics Blocking Reasons | Tool to retrieve blocking reasons analytics showing blocklists, native tracking protection, and other reasons for blocked queries. Use after selecting a profile to understand what categories are blocking queries. |
| `NEXTDNS_GET_ANALYTICS_STATUS` | Get Analytics Status | Tool to retrieve analytics status for a specific profile. Use when you need counts of DNS queries broken down by status categories. |
| `NEXTDNS_GET_LOGS` | Get Logs | Tool to retrieve logs for a specific NextDNS profile with optional filters. Use after confirming the profile ID to fetch raw or filtered DNS logs. |
| `NEXTDNS_GET_PARENTAL_CONTROL` | Get Parental Control Settings | Tool to get parental control settings for a profile. Returns services, categories, safe search, YouTube restricted mode, and bypass blocking status. |
| `NEXTDNS_GET_PARENTAL_CONTROL_CATEGORIES` | Get Parental Control Categories | Tool to get the list of blocked/allowed content categories for parental control. Use when you need to check which content categories are currently blocked or allowed for a specific profile. |
| `NEXTDNS_GET_PARENTAL_CONTROL_SERVICES` | Get Parental Control Services | Tool to get the list of blocked/allowed services for parental control. Use when you need to review which services (like TikTok, Facebook, Netflix) are currently blocked or allowed in a profile's parental control settings. |
| `NEXTDNS_GET_PERFORMANCE_SETTINGS` | Get Performance Settings | Tool to get performance settings for a profile including ECS, cache boost, and CNAME flattening configuration. Use when you need to check current performance optimization settings before making changes. |
| `NEXTDNS_GET_PRIVACY_SETTINGS` | Get Privacy Settings | Tool to get privacy settings for a profile including blocklists, native tracking settings, disguised trackers, and affiliate settings. Use when you need to check the current privacy configuration before making changes. |
| `NEXTDNS_GET_PROFILE` | Get Profile Details | Retrieves the details of a specific NextDNS profile. It requires a 'profileId' as a path parameter and returns the profile details including name, security, privacy, parental control, denylist, allowlist, and general settings. |
| `NEXTDNS_GET_REWRITES` | Get DNS Rewrites | Tool to retrieve the list of DNS rewrites for a NextDNS profile. Use when you need to view all custom DNS rewrite rules configured in a profile. |
| `NEXTDNS_GET_SECURITY_TLDS` | Get Security TLDs | Tool to get the list of blocked TLDs (top-level domains) for a profile's security settings. Use when you need to retrieve only the blocked TLDs without fetching all security settings. |
| `NEXTDNS_GET_SETTINGS` | Get Profile Settings | Tool to get all settings for a NextDNS profile including logs, block page, performance, and web3 settings. Use when you need to retrieve the current configuration settings of a profile. |
| `NEXTDNS_GET_SETTINGS_BLOCKPAGE` | Get Block Page Settings | Tool to retrieve the block page settings for a NextDNS profile. Use when you need to check if the block page is currently enabled or disabled for a specific profile. |
| `NEXTDNS_GET_SETTINGS_LOGS` | Get Logging Settings | Tool to retrieve the logging settings for a NextDNS profile. Use when you need to check logging status, data retention period, storage location, or privacy options. |
| `NEXTDNS_LIST_DENYLIST_DOMAINS` | List Denylist Domains | Tool to list domains in the denylist for a profile. Use after confirming the profile ID to review all blocked domains. Example: "List denylist domains for profile abc123." |
| `NEXTDNS_LIST_PROFILES` | List Profiles | List all NextDNS profiles for the authenticated user, returning profile IDs and configurations. Returns all profiles with their IDs, names, fingerprints, and user roles. Profile IDs returned by this action are used as the 'profileId' or 'config_id' parameter for other NextDNS actions (e.g., get profile details, update profile, etc.). |
| `NEXTDNS_LIST_SECURITY_SETTINGS` | List Security Settings | Tool to list current security options for a NextDNS configuration. Use after obtaining the configuration ID to review active security settings. |
| `NEXTDNS_LOG_CLIENT_IPS` | Log Client IPs | Tool to enable or disable logging of client IPs for a NextDNS configuration. Use when you need to toggle whether client IPs are recorded in DNS logs. |
| `NEXTDNS_LOG_DOMAINS` | Toggle Domain Logging | Tool to enable or disable logging of domains for a NextDNS profile. Use after retrieving profile settings when you need to adjust domain logging. Example: "Enable domain logging for profile abc123." |
| `NEXTDNS_REMOVE_BLOCKED_TLD` | Remove Blocked TLD | Tool to remove a top-level domain from the security blocklist for a NextDNS profile. Use after listing current security settings to confirm the TLD is currently blocked. |
| `NEXTDNS_REMOVE_DENYLIST_DOMAIN` | Remove Denylist Domain | Removes a domain from a NextDNS profile's denylist (blocklist). The domain will no longer be blocked by the DNS filter after removal. Use 'List Denylist Domains' first to verify the domain exists in the denylist before attempting removal. |
| `NEXTDNS_RENAME_CONFIG` | Rename Configuration | Tool to rename a NextDNS configuration (profile). Use when you need to update a profile's name after obtaining its ID. Example: RenameConfig(name="Home Profile", config_id="d46a5b") |
| `NEXTDNS_REPLACE_ALLOWLIST` | Replace Allowlist | Tool to replace the entire allowlist for a NextDNS profile. Use when you need to set a complete list of allowed domains, replacing all existing entries. |
| `NEXTDNS_REPLACE_DENYLIST` | Replace Denylist | Tool to replace the entire denylist (blocked domains) for a NextDNS profile. This operation completely replaces all existing denylist entries with the provided list. Use when you need to bulk update the denylist or clear all blocked domains. To add/remove individual domains, use NEXTDNS_ADD_DENYLIST_DOMAIN or NEXTDNS_REMOVE_DENYLIST_DOMAIN instead. |
| `NEXTDNS_REPLACE_PARENTAL_CONTROL_CATEGORIES` | Replace Parental Control Categories | Tool to replace the entire list of blocked/allowed content categories for parental control. Use this to set which content categories should be blocked or allowed for a profile. |
| `NEXTDNS_REPLACE_PARENTAL_CONTROL_SERVICES` | Replace Parental Control Services | Tool to replace the entire list of blocked/allowed services for parental control. Use when you need to set all service restrictions at once, replacing existing settings. |
| `NEXTDNS_REPLACE_PRIVACY_BLOCKLISTS` | Replace Privacy Blocklists | Tool to replace the entire list of privacy blocklists for a NextDNS profile. This operation completely replaces all existing blocklists with the provided list. Use when you need to bulk update privacy blocklists or clear all blocklists. |
| `NEXTDNS_REPLACE_PRIVACY_NATIVES` | Replace Privacy Native Tracking Services | Tool to replace the entire list of blocked native tracking services for a NextDNS profile. This operation completely replaces all existing native tracking service blocks with the provided list. Use when you need to bulk update blocked native trackers or clear all blocks. |
| `NEXTDNS_REPLACE_SECURITY_TLDS` | Replace Security TLDs | Tool to replace the entire list of blocked TLDs (top-level domains) for a NextDNS profile's security settings. This operation completely replaces all existing blocked TLDs with the provided list. Use when you need to bulk update blocked TLDs or clear all TLD blocks. To add/remove individual TLDs, use NEXTDNS_ADD_BLOCKED_TLD or NEXTDNS_REMOVE_BLOCKED_TLD instead. |
| `NEXTDNS_UPDATE_ALLOWLIST_ENTRY` | Update Allowlist Entry | Tool to update a specific allowlist entry in a NextDNS profile. Use when toggling the active status of a domain in the allowlist. |
| `NEXTDNS_UPDATE_DENYLIST_ENTRY` | Update Denylist Entry | Updates a specific denylist entry in a NextDNS profile, typically to toggle its active status. Use when you need to temporarily enable or disable blocking for a domain without removing it from the denylist. |
| `NEXTDNS_UPDATE_LINKED_IP` | Update linked IP | Updates the linked IP address for a NextDNS profile to the current caller's public IP. This is used for dynamic DNS setups where the profile needs to recognize the user's current IP address for DNS filtering to work properly. |
| `NEXTDNS_UPDATE_PARENTAL_CONTROL` | Update Parental Control Settings | Tool to update parental control settings for a NextDNS profile. Use when you need to change safe search, YouTube restricted mode, or bypass blocking settings. |
| `NEXTDNS_UPDATE_PARENTAL_CONTROL_CATEGORY` | Update Parental Control Category | Tool to update a specific category entry in parental control settings. Use when you need to enable or disable blocking for a specific content category like pornography, gambling, or social networks. |
| `NEXTDNS_UPDATE_PARENTAL_CONTROL_SERVICE` | Update Parental Control Service | Tool to update a specific service entry in parental control settings. Use when toggling individual service blocks (e.g., blocking TikTok, Instagram, or other social media/gaming services). |
| `NEXTDNS_UPDATE_PERFORMANCE_SETTINGS` | Update Performance Settings | Tool to update performance settings of a NextDNS profile. Use when adjusting performance optimizations after reviewing current settings. |
| `NEXTDNS_UPDATE_PRIVACY_SETTINGS` | Update Privacy Settings | Tool to update privacy settings for a profile. Use when you need to change blocklists, native trackers, disguisedTrackers, or allowAffiliate in one call. |
| `NEXTDNS_UPDATE_SECURITY_SETTINGS` | Update Security Settings | Tool to update security settings for a profile. Use when you need to change multiple security settings like threat intelligence, AI detection, safe browsing, and other protections in one call. |
| `NEXTDNS_UPDATE_SETTINGS` | Update Settings | Tool to update settings for a NextDNS profile including logs, block page, performance, and web3 settings. Use when you need to modify multiple settings categories in one operation. Only provide the specific settings you want to change - all fields are optional except profile ID. |
| `NEXTDNS_UPDATE_SETTINGS_BLOCKPAGE` | Update Block Page Settings | Tool to update block page settings for a NextDNS profile. Use when you need to enable or disable the branded block page that users see when accessing blocked domains. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Nextdns MCP server is an implementation of the Model Context Protocol that connects Claude Code (and other AI assistants like Claude and Cursor) directly to your Nextdns account. It provides structured and secure access so Claude can perform Nextdns operations on your behalf.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- Claude Pro, Max, or API billing enabled Anthropic account
- Composio API Key
- A Nextdns account
- Basic knowledge of Python or TypeScript

### 1. Install Claude Code

To install Claude Code, use one of the following methods based on your operating system:
```bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd
```

### 2. Set up Claude Code

Open a terminal, go to your project folder, and start Claude Code:
- Claude Code will open in your terminal
- Follow the prompts to sign in with your Anthropic account
- Complete the authentication flow
- Once authenticated, you can start using Claude Code
```bash
cd your-project-folder
claude
```

### 3. Set up environment variables

Create a .env file in your project root with the following variables:
- COMPOSIO_API_KEY authenticates with Composio (get it from [Composio dashboard](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=api_key&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code))
- USER_ID identifies the user for session management (use any unique identifier)
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
```

### 4. Install Composio library

No description provided.
```python
pip install composio-core python-dotenv
```

```typescript
npm install @composio/core dotenv
```

### 5. Generate Composio MCP URL

No description provided.
```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["nextdns"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http nextdns-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['nextdns'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http nextdns-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

### 6. Run the script and copy the MCP URL

No description provided.
```python
python generate_mcp_url.py
```

```typescript
node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts
```

### 7. Add Nextdns MCP to Claude Code

In your terminal, add the MCP server using the command from the previous step. The command format is:
- claude mcp add registers a new MCP server with Claude Code
- --transport http specifies that this is an HTTP-based MCP server
- The server name (nextdns-composio) is how you'll reference it
- The URL points to your Composio Tool Router session
- --headers includes your Composio API key for authentication
After running the command, close the current Claude Code session and start a new one for the changes to take effect.
```bash
claude mcp add --transport http nextdns-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude
```

### 8. Verify the installation

Check that your Nextdns MCP server is properly configured.
- This command lists all MCP servers registered with Claude Code
- You should see your nextdns-composio entry in the list
- This confirms that Claude Code can now access Nextdns tools
If everything is wired up, you should see your nextdns-composio entry listed:
```bash
claude mcp list
```

### 9. Authenticate Nextdns

The first time you try to use Nextdns tools, you'll be prompted to authenticate.
- Claude Code will detect that you need to authenticate with Nextdns
- It will show you an authentication link
- Open the link in your browser (or copy/paste it)
- Complete the Nextdns authorization flow
- Return to the terminal and start using Nextdns through Claude Code
Once authenticated, you can ask Claude Code to perform Nextdns operations in natural language. For example:
- "Block access to adult websites for a profile"
- "Download DNS logs from last week"
- "Show top domains queried by my devices"

## Complete Code

```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["nextdns"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http nextdns-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['nextdns'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http nextdns-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

## Conclusion

You've successfully integrated Nextdns with Claude Code using Composio's MCP server. Now you can interact with Nextdns directly from your terminal using natural language commands.
Key features of this setup:
- Terminal-native experience without switching contexts
- Natural language commands for Nextdns operations
- Secure authentication through Composio's managed MCP
- Tool Router for dynamic tool discovery and execution
Next steps:
- Try asking Claude Code to perform various Nextdns operations
- Add more toolkits to your Tool Router session for multi-app workflows
- Integrate this setup into your development workflow for increased productivity
You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

## How to build Nextdns MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/nextdns/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/nextdns/framework/claude-agents-sdk)
- [Claude Cowork](https://composio.dev/toolkits/nextdns/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/nextdns/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/nextdns/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/nextdns/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/nextdns/framework/cli)
- [Google ADK](https://composio.dev/toolkits/nextdns/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/nextdns/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/nextdns/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/nextdns/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/nextdns/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/nextdns/framework/crew-ai)

## Related Toolkits

- [Excel](https://composio.dev/toolkits/excel) - 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](https://composio.dev/toolkits/_21risk) - 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](https://composio.dev/toolkits/abstract) - 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.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Agenty](https://composio.dev/toolkits/agenty) - Agenty is a web scraping and automation platform for extracting data and automating browser tasks—no coding needed. It streamlines data collection, monitoring, and repetitive online actions.
- [Ambee](https://composio.dev/toolkits/ambee) - Ambee is an environmental data platform providing real-time, hyperlocal APIs for air quality, weather, and pollen. Get precise environmental insights to power smarter decisions in your apps and workflows.
- [Ambient weather](https://composio.dev/toolkits/ambient_weather) - Ambient Weather is a platform for personal weather stations with a robust API for accessing local, real-time, and historical weather data. Get detailed environmental insights directly from your own sensors for smarter apps and automations.
- [Anonyflow](https://composio.dev/toolkits/anonyflow) - Anonyflow is a service for encryption-based data anonymization and secure data sharing. It helps organizations meet GDPR, CCPA, and HIPAA data privacy compliance requirements.
- [Api ninjas](https://composio.dev/toolkits/api_ninjas) - Api ninjas offers 120+ public APIs spanning categories like weather, finance, sports, and more. Developers use it to supercharge apps with real-time data and actionable endpoints.
- [Api sports](https://composio.dev/toolkits/api_sports) - Api sports is a comprehensive sports data platform covering 2,000+ competitions with live scores and 15+ years of stats. Instantly access up-to-date sports information for analysis, apps, or chatbots.
- [Apify](https://composio.dev/toolkits/apify) - Apify is a cloud platform for building, deploying, and managing web scraping and automation tools called Actors. It lets you automate data extraction and workflow tasks at scale—no infrastructure headaches.
- [Autom](https://composio.dev/toolkits/autom) - Autom is a lightning-fast search engine results data platform for Google, Bing, and Brave. Developers use it to access fresh, low-latency SERP data on demand.
- [Beaconchain](https://composio.dev/toolkits/beaconchain) - Beaconchain is a real-time analytics platform for Ethereum 2.0's Beacon Chain. It provides detailed insights into validators, blocks, and overall network performance.
- [Big data cloud](https://composio.dev/toolkits/big_data_cloud) - BigDataCloud provides APIs for geolocation, reverse geocoding, and address validation. Instantly access reliable location intelligence to enhance your applications and workflows.
- [Bigpicture io](https://composio.dev/toolkits/bigpicture_io) - BigPicture.io offers APIs for accessing detailed company and profile data. Instantly enrich your applications with up-to-date insights on 20M+ businesses.
- [Bitquery](https://composio.dev/toolkits/bitquery) - Bitquery is a blockchain data platform offering indexed, real-time, and historical data from 40+ blockchains via GraphQL APIs. Get unified, reliable access to complex on-chain data for analytics, trading, and research.
- [Brightdata](https://composio.dev/toolkits/brightdata) - Brightdata is a leading web data platform offering advanced scraping, SERP APIs, and anti-bot tools. It lets you collect public web data at scale, bypassing blocks and friction.
- [Builtwith](https://composio.dev/toolkits/builtwith) - BuiltWith is a web technology profiler that uncovers the technologies powering any website. Gain actionable insights into analytics, hosting, and content management stacks for smarter research and lead generation.
- [Byteforms](https://composio.dev/toolkits/byteforms) - Byteforms is an all-in-one platform for creating forms, managing submissions, and integrating data. It streamlines workflows by centralizing form data collection and automation.
- [Cabinpanda](https://composio.dev/toolkits/cabinpanda) - Cabinpanda is a data collection platform for building and managing online forms. It helps streamline how you gather, organize, and analyze responses.

## Frequently Asked Questions

### 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 Code?

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

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)