How to integrate Nextdns MCP with Codex

Framework Integration Gradient
Nextdns Logo
Codex Logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Nextdns MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or app, whichever you prefer.

Composio removes the Authentication handling completely from you. We handle the entire integration lifecycle, and all you need to do is just copy the URL below, authenticate inside Codex, and start using it.

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 870+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Nextdns MCP in Codex

Codex CLI

Run the command in your terminal.

Terminal

This will auto-redirect you to the Rube authentication page.

Rube authentication redirect page

Once you're authenticated, you will be able to access the tools.

Verify the installation by running:

codex mcp list

If you otherwise prefer to use config.toml, add the following URL to it. You can get the bearer token from rube.app → Use Rube → MCP URL → Generate token

[projects."/home/user/composio"]
trust_level = "untrusted"

[mcp_servers.rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex in VS Code

If you have installed Codex in VS Code.

Then: ⚙️ → MCP Settings → + Add servers → Streamable HTTP:

Add the Rube MCP URL: https://rube.app/mcp and the bearer token.

VS Code MCP Settings

To verify, click on the Open config.toml

Open config toml in Codex

Make sure it's there:

[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
Codex App MCP Settings
  1. Restart and verify if it's there in .codex/config.toml
[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"
  1. Save, restart the extension, and start working.

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.

Conclusion

You've successfully integrated Nextdns with Codex using Composio's Rube MCP server. Now you can interact with Nextdns directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for Nextdns operations
  • Managed authentication through Composio's Rube
  • Access to 20,000+ tools across 870+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Nextdns operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build Nextdns MCP Agent with another framework

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 Codex?

Yes, you can. Codex 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
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
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.