How to integrate Control d MCP with Mastra AI

This guide walks you through connecting Control d to Mastra AI using the Composio tool router. By the end, you'll have a working Control d agent that can list all devices connected to your account, remove a device by its id, show known access ips for your network through natural language commands. This guide will help you understand how to give your Mastra AI agent real control over a Control d account through Composio's Control d MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for freeGet a demo
Control d logoControl d
Api Key

Control d is a customizable DNS filtering and traffic redirection platform. It helps you manage internet access, enforce policies, and monitor usage across devices and networks.

54 Tools

Introduction

This guide walks you through connecting Control d to Mastra AI using the Composio tool router. By the end, you'll have a working Control d agent that can list all devices connected to your account, remove a device by its id, show known access ips for your network through natural language commands.

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

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

Also integrate Control d with

OpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKLlamaIndexCrewAI

TL;DR

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

What is Mastra AI?

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

Key features include:

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

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

The Control d MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Control d account. It provides structured and secure access to your DNS filtering and device management environment, so your agent can perform actions like managing devices, enforcing policies, retrieving analytics, and monitoring network access on your behalf.

  • Device inventory management: Easily list all devices on your account or remove specific devices by their identifier for streamlined device control.
  • Profile and rule administration: Direct your agent to delete profiles, custom rules, or schedules—helping you maintain and enforce up-to-date network policies.
  • Network access monitoring: Retrieve a list of known access IPs to keep tabs on which endpoints are connecting to your network infrastructure.
  • Analytics endpoints discovery: Quickly fetch available analytics storage regions and endpoints so you can integrate and analyze DNS traffic data efficiently.
  • Organization details access: Have the agent fetch and present your organization's account details for easy reference and auditing.

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:

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

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

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

Getting API Keys for OpenAI and Composio

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

Install dependencies

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

Install the required packages.

What's happening:

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

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

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

Import libraries and validate environment

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

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

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

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

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

Create a Tool Router session for Control d

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

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

Configure Mastra MCP client and fetch tools

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

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

Create the Mastra agent

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

Set up interactive chat interface

typescript
let messages: AiMessageType[] = [];

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

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

rl.prompt();

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

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

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

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

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

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

    const { text } = response;

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

    rl.prompt();
  });

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

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

Complete Code

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

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

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

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

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

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

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

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

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

  let messages: AiMessageType[] = [];

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

  rl.prompt();

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

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

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

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

    rl.prompt();
  });

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

main();

Conclusion

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

Supported Tools

Every Control d action and event your agent gets out of the box.

Delete Device by ID

Permanently delete a Control-D device/endpoint by its ID.

Delete Profile

Permanently deletes a Control D profile by its unique identifier (PK).

Delete Profile Rule by Rule ID

Delete a custom DNS rule from a Control D profile by its rule identifier (hostname/domain).

Delete Rule from Folder

Delete a custom DNS rule from a specific folder in a Control D profile.

Delete Profile Schedule

Tool to delete a specific schedule within a profile.

List Known Access IPs

List up to the latest 50 IP addresses that were used to query against a specific Device (resolver).

Get Analytics Endpoints

Tool to list analytics storage regions and their endpoints.

Get Analytics Levels

Tool to retrieve available analytics log levels for Control D devices.

Get Billing Payments

Tool to retrieve billing history of all payments made.

Get Billing Products

Retrieve all products currently activated on the Control D account.

Get Devices

Lists all Control D devices (endpoints) associated with the account.

Get Device Types

List all allowed device types in Control D.

Get IP

Tool to retrieve the current IP address and datacenter information for the API request.

Get Network Stats

Tool to retrieve network stats on available services in different POPs (Points of Presence).

Get Organization Members

Tool to view organization membership.

Get Organization Details

Tool to view the authenticated organization's details.

Get Sub-Organizations

Tool to view sub-organizations and their details.

Get Profiles

Tool to list all profiles associated with the authenticated account.

Get Profile Options

Retrieves all available configuration options for DNS profiles in Control D.

Get Profile by ID

Tool to retrieve details of a specific profile by its ID.

Get Profile Analytics

Retrieve analytics data for a Control D profile.

Get Profile Analytics Logs

Retrieves DNS query activity logs for a specific Control D profile.

Get Analytics Log Entry

Tool to retrieve a specific analytics log entry by its ID.

Get Profile Analytics Summary

Tool to fetch a summary of analytics data for a given profile.

Get Profile Analytics Top Domains

Tool to fetch top domains accessed within a specific profile.

Get Profile Top Services

Tool to fetch top services accessed within a profile.

Get Profile Filters

List all native (Control D curated) filters for a profile and their current states.

List External Filters for Profile

Tool to list third-party filters for a specific profile.

Get Profile Folders

List all rule folders (groups) within a Control D profile.

List Custom DNS Rules for Profile

Retrieve custom DNS rules for a Control D profile.

Get Specific Rule in Folder

Tool to retrieve a specific rule within a folder by its ID.

Get Profile Schedules

Tool to list schedules associated with a specific profile.

Get Profile Schedule

Tool to retrieve a specific schedule by its ID within a profile.

Get Profile Services

Tool to list services associated with a specific profile.

Get Proxies

Tool to retrieve the list of usable proxy locations that traffic can be redirected through.

Get Service Categories

List all available service categories in Control D.

List Services by Category

Retrieves all services within a specific ControlD service category.

Get Users

Retrieve the authenticated user's account information from Control D.

Create Device

Create a new device (DNS endpoint) in Control D.

Create Profile

Create a new blank profile or clone an existing one.

Create Custom DNS Rule

Create custom DNS rules for a profile to control domain resolution.

Create Custom Rules in Profile Folder

Tool to create custom rules within a specific folder for a profile.

Create Profile Schedule

Create a new time-based schedule within a Control D profile.

Modify Device

Modify an existing Control D device's settings.

Modify Organization

Modify organization settings such as name, contact details, website, and device limits.

Modify Profile

Modify an existing profile by its ID.

Bulk Update Profile Filters

Tool to bulk update filters on a specific profile.

Update External Filters for Profile

Tool to update external filters for a specific profile.

Modify Profile Filter

Modify the enabled state of a specific native filter on a profile.

Modify Custom Rule for Profile

Modify an existing custom DNS rule for a profile in Control D.

Update Custom Rule by Rule ID

Tool to update an existing custom rule by its ID.

Move Profile Rule to Folder

Tool to move a specific custom rule into a different folder.

Update Profile Schedule

Tool to update a specific schedule within a profile.

Modify Service for Profile

Tool to modify a specific service rule for a profile.

FRAMEWORKS

How to build Control d MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Control d MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Control d MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Control d MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Control d MCP with Claude Cowork

Codex logo

Codex

Use Control d MCP with Codex

OpenClaw logo

OpenClaw

Use Control d MCP with OpenClaw

Hermes logo

Hermes

Use Control d MCP with Hermes

CLI logo

CLI

Use Control d MCP with CLI

Google ADK logo

Google ADK

Use Control d MCP with Google ADK

LangChain logo

LangChain

Use Control d MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Control d MCP with Vercel AI SDK

LlamaIndex logo

LlamaIndex

Use Control d MCP with LlamaIndex

CrewAI logo

CrewAI

Use Control d MCP with CrewAI

FAQ

Frequently asked questions

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

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

Yes, absolutely. You can configure which Control d 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.

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 Control d data and credentials are handled as safely as possible.

Start with Control d.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Control d tool your agent needs.Free to start.

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

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

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

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's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

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

Nirman Dave
Nirman Dave
CEO, Zams

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

Ryan Yu
Ryan Yu
Founder, Extra Thursday

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

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

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.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies