Nextdns with Vercel AI SDK

How to integrate Nextdns MCP with Vercel AI SDK v6

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 Vercel AI 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 Vercel AI SDK v6 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 Vercel AI 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 Agent SDK Claude Code Claude Cowork Codex OpenClaw Hermes CLI Google ADK LangChain Mastra AI LlamaIndex CrewAI

TL;DR

Here's what you'll learn:

How to set up and configure a Vercel AI SDK agent with Nextdns integration
Using Composio's Tool Router to dynamically load and access Nextdns tools
Creating an MCP client connection using HTTP transport
Building an interactive CLI chat interface with conversation history management
Handling tool calls and results within the Vercel AI SDK framework

What is Vercel AI SDK?

The Vercel AI SDK is a TypeScript library for building AI-powered applications. It provides tools for creating agents that can use external services and maintain conversation state.

Key features include:

streamText: Core function for streaming responses with real-time tool support
MCP Client: Built-in support for Model Context Protocol via @ai-sdk/mcp
Step Counting: Control multi-step tool execution with stopWhen: stepCountIs()
OpenAI Provider: Native integration with OpenAI models

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 you begin, make sure you have:

Node.js and npm installed
A Composio account with API key
An OpenAI API key

Getting API Keys for OpenAI and Composio

OpenAI API Key

Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
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 required dependencies

bash

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

First, install the necessary packages for your project.

What you're installing:

@ai-sdk/openai: Vercel AI SDK's OpenAI provider
@ai-sdk/mcp: MCP client for Vercel AI SDK
@composio/core: Composio SDK for tool integration
ai: Core Vercel AI SDK
dotenv: Environment variable management

Set up environment variables

bash

OPENAI_API_KEY=your_openai_api_key_here
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here

Create a .env file in your project root.

What's needed:

OPENAI_API_KEY: Your OpenAI API key for GPT model access
COMPOSIO_API_KEY: Your Composio API key for tool access
COMPOSIO_USER_ID: A unique identifier for the user session

Import required modules and validate environment

typescript

import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Composio } from "@composio/core";
import * as readline from "readline";
import { streamText, type ModelMessage, stepCountIs } from "ai";
import { createMCPClient } from "@ai-sdk/mcp";

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

if (!process.env.OPENAI_API_KEY) 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,
});

What's happening:

We're importing all necessary libraries including Vercel AI SDK's OpenAI provider and Composio
The dotenv/config import automatically loads environment variables
The MCP client import enables connection to Composio's tool server

Create Tool Router session and initialize MCP client

typescript

async function main() {
  // Create a tool router session for the user
  const session = await composio.create(composioUserID!, {
    toolkits: ["nextdns"],
  });

  const mcpUrl = session.mcp.url;

What's happening:

We're creating a Tool Router session that gives your agent access to Nextdns tools
The create method takes the user ID and specifies which toolkits should be available
The returned mcp object contains the URL and authentication headers needed to connect to the MCP server
This session provides access to all Nextdns-related tools through the MCP protocol

Connect to MCP server and retrieve tools

typescript

const mcpClient = await createMCPClient({
  transport: {
    type: "http",
    url: mcpUrl,
    headers: session.mcp.headers, // Authentication headers for the Composio MCP server
  },
});

const tools = await mcpClient.tools();

What's happening:

We're creating an MCP client that connects to our Composio Tool Router session via HTTP
The mcp.url provides the endpoint, and mcp.headers contains authentication credentials
The type: "http" is important - Composio requires HTTP transport
tools() retrieves all available Nextdns tools that the agent can use

Initialize conversation and CLI interface

typescript

let messages: ModelMessage[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log(
  "Ask any questions related to nextdns, like summarize my last 5 emails, send an email, etc... :)))\n",
);

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

rl.prompt();

What's happening:

We initialize an empty messages array to maintain conversation history
A readline interface is created to accept user input from the command line
Instructions are displayed to guide the user on how to interact with the agent

Handle user input and stream responses with real-time tool feedback

typescript

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({ role: "user", content: trimmedInput });
  console.log("\nAgent is thinking...\n");

  try {
    const stream = streamText({
      model: openai("gpt-5"),
      messages,
      tools,
      toolChoice: "auto",
      stopWhen: stepCountIs(10),
      onStepFinish: (step) => {
        for (const toolCall of step.toolCalls) {
          console.log(`[Using tool: ${toolCall.toolName}]`);
          }
          if (step.toolCalls.length > 0) {
            console.log(""); // Add space after tool calls
          }
        },
      });

      for await (const chunk of stream.textStream) {
        process.stdout.write(chunk);
      }

      console.log("\n\n---\n");

      // Get final result for message history
      const response = await stream.response;
      if (response?.messages?.length) {
        messages.push(...response.messages);
      }
    } catch (error) {
      console.error("\nAn error occurred while talking to the agent:");
      console.error(error);
      console.log(
        "\nYou can try again or restart the app if it keeps happening.\n",
      );
    } finally {
      rl.prompt();
    }
  });

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

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});

What's happening:

We use streamText instead of generateText to stream responses in real-time
toolChoice: "auto" allows the model to decide when to use Nextdns tools
stopWhen: stepCountIs(10) allows up to 10 steps for complex multi-tool operations
onStepFinish callback displays which tools are being used in real-time
We iterate through the text stream to create a typewriter effect as the agent responds
The complete response is added to conversation history to maintain context
Errors are caught and displayed with helpful retry suggestions

Complete Code

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

typescript

import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Composio } from "@composio/core";
import * as readline from "readline";
import { streamText, type ModelMessage, stepCountIs } from "ai";
import { createMCPClient } from "@ai-sdk/mcp";

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

if (!process.env.OPENAI_API_KEY) 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,
});

async function main() {
  // Create a tool router session for the user
  const session = await composio.create(composioUserID!, {
    toolkits: ["nextdns"],
  });

  const mcpUrl = session.mcp.url;

  const mcpClient = await createMCPClient({
    transport: {
      type: "http",
      url: mcpUrl,
      headers: session.mcp.headers, // Authentication headers for the Composio MCP server
    },
  });

  const tools = await mcpClient.tools();

  let messages: ModelMessage[] = [];

  console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
  console.log(
    "Ask any questions related to nextdns, like summarize my last 5 emails, send an email, etc... :)))\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({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    try {
      const stream = streamText({
        model: openai("gpt-5"),
        messages,
        tools,
        toolChoice: "auto",
        stopWhen: stepCountIs(10),
        onStepFinish: (step) => {
          for (const toolCall of step.toolCalls) {
            console.log(`[Using tool: ${toolCall.toolName}]`);
          }
          if (step.toolCalls.length > 0) {
            console.log(""); // Add space after tool calls
          }
        },
      });

      for await (const chunk of stream.textStream) {
        process.stdout.write(chunk);
      }

      console.log("\n\n---\n");

      // Get final result for message history
      const response = await stream.response;
      if (response?.messages?.length) {
        messages.push(...response.messages);
      }
    } catch (error) {
      console.error("\nAn error occurred while talking to the agent:");
      console.error(error);
      console.log(
        "\nYou can try again or restart the app if it keeps happening.\n",
      );
    } finally {
      rl.prompt();
    }
  });

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

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});

Conclusion

You've successfully built a Nextdns agent using the Vercel AI SDK with streaming capabilities! This implementation provides a powerful foundation for building AI applications with natural language interfaces and real-time feedback.

Key features of this implementation:

Real-time streaming responses for a better user experience with typewriter effect
Live tool execution feedback showing which tools are being used as the agent works
Dynamic tool loading through Composio's Tool Router with secure authentication
Multi-step tool execution with configurable step limits (up to 10 steps)
Comprehensive error handling for robust agent execution
Conversation history maintenance for context-aware responses

You can extend this further by adding custom error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.

How to build Nextdns MCP Agent with another framework

OpenAI Agents SDK

Use Nextdns MCP with OpenAI Agents SDK

Claude Agent SDK

Use Nextdns MCP with Claude Agent 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

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 Vercel AI SDK v6?

Yes, you can. Vercel AI SDK v6 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 Vercel AI SDK v6

Table of Contents

Connect Nextdns without Auth hassles

Introduction

Also integrate Nextdns with

TL;DR

What is Vercel AI 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 OpenAI and Composio

Install required dependencies

Set up environment variables

Import required modules and validate environment

Create Tool Router session and initialize MCP client

Connect to MCP server and retrieve tools

Initialize conversation and CLI interface

Handle user input and stream responses with real-time tool feedback

Complete Code

Conclusion

How to build Nextdns MCP Agent with another framework

OpenAI Agents SDK

Claude Agent SDK

Claude Code

Claude Cowork

Codex

OpenClaw

Hermes

CLI

Google ADK

LangChain

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 Vercel AI SDK v6?

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