How to integrate Control d MCP with OpenAI Agents SDK

This guide walks you through connecting Control d to the OpenAI Agents SDK 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 OpenAI Agents SDK 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 the OpenAI Agents SDK 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 OpenAI Agents SDK 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

Claude Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Control d
  • Configure an AI agent that can use Control d as a tool
  • Run a live chat session where you can ask the agent to perform Control d operations

What is OpenAI Agents SDK?

The OpenAI Agents SDK is a lightweight framework for building AI agents that can use tools and maintain conversation state. It provides a simple interface for creating agents with hosted MCP tool support.

Key features include:

  • Hosted MCP Tools: Connect to external services through hosted MCP endpoints
  • SQLite Sessions: Persist conversation history across interactions
  • Simple API: Clean interface with Agent, Runner, and tool configuration
  • Streaming Support: Real-time response streaming for interactive applications

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:
  • Composio API Key and OpenAI API Key
  • Primary know-how of OpenAI Agents SDK
  • A live Control d project
  • Some knowledge of Python or Typescript
2

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
3

Install dependencies

npm install @composio/openai-agents @openai/agents dotenv

Install the Composio SDK and the OpenAI Agents SDK.

4

Set up environment variables

bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com

Create a .env file and add your OpenAI and Composio API keys.

5

Import dependencies

import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';
What's happening:
  • You're importing all necessary libraries.
  • The Composio and OpenAIAgentsProvider classes are imported to connect your OpenAI agent to Composio tools like Control d.
6

Set up the Composio instance

dotenv.config();

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});
What's happening:
  • dotenv.config() loads your .env file so COMPOSIO_API_KEY and USER_ID are available as environment variables.
  • Creating a Composio instance using the API Key and OpenAIAgentsProvider class.
7

Create a Tool Router session

// Create Tool Router session for Control d
const session = await composio.create(userId as string, {
  toolkits: ['control_d'],
});
const mcpUrl = session.mcp.url;

What is happening:

  • You give the Tool Router the user id and the toolkits you want available. Here, it is only control_d.
  • The router checks the user's Control d connection and prepares the MCP endpoint.
  • The returned session.mcp.url is the MCP URL that your agent will use to access Control d.
  • This approach keeps things lightweight and lets the agent request Control d tools only when needed during the conversation.
8

Configure the agent

// Configure agent with MCP tool
const agent = new Agent({
  name: 'Assistant',
  model: 'gpt-5',
  instructions:
    'You are a helpful assistant that can access Control d. Help users perform Control d operations through natural language.',
  tools: [
    hostedMcpTool({
      serverLabel: 'tool_router',
      serverUrl: mcpUrl,
      headers: { 'x-api-key': composioApiKey },
      requireApproval: 'never',
    }),
  ],
});
What's happening:
  • We're creating an Agent instance with a name, model (gpt-5), and clear instructions about its purpose.
  • The agent's instructions tell it that it can access Control d and help with queries, inserts, updates, authentication, and fetching database information.
  • The tools array includes a hostedMcpTool that connects to the MCP server URL we created earlier.
  • The headers object includes the Composio API key for secure authentication with the MCP server.
  • requireApproval: 'never' means the agent can execute Control d operations without asking for permission each time, making interactions smoother.
9

Start chat loop and handle conversation

// Keep conversation state across turns
const conversationSession = new OpenAIConversationsSession();

// Simple CLI
const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: 'You: ',
});

console.log('\nComposio Tool Router session created.');
console.log('\nChat started. Type your requests below.');
console.log("Commands: 'exit', 'quit', or 'q' to end\n");

try {
  const first = await run(agent, 'What can you help me with?', { session: conversationSession });
  console.log(`Assistant: ${first.finalOutput}\n`);
} catch (e) {
  console.error('Error:', e instanceof Error ? e.message : e, '\n');
}

rl.prompt();

rl.on('line', async (userInput) => {
  const text = userInput.trim();

  if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
    console.log('Goodbye!');
    rl.close();
    process.exit(0);
  }

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

  try {
    const result = await run(agent, text, { session: conversationSession });
    console.log(`\nAssistant: ${result.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();
});

rl.on('close', () => {
  console.log('\n👋 Session ended.');
  process.exit(0);
});
What's happening:
  • The program prints a session URL that you visit to authorize Control d.
  • After authorization, the chat begins.
  • Each message you type is processed by the agent using run().
  • The responses are printed to the console.
  • Typing exit, quit, or q cleanly ends the chat.

Complete Code

Here's the complete code to get you started with Control d and OpenAI Agents SDK:

import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});

async function main() {
  // Create Tool Router session
  const session = await composio.create(userId as string, {
    toolkits: ['control_d'],
  });
  const mcpUrl = session.mcp.url;

  // Configure agent with MCP tool
  const agent = new Agent({
    name: 'Assistant',
    model: 'gpt-5',
    instructions:
      'You are a helpful assistant that can access Control d. Help users perform Control d operations through natural language.',
    tools: [
      hostedMcpTool({
        serverLabel: 'tool_router',
        serverUrl: mcpUrl,
        headers: { 'x-api-key': composioApiKey },
        requireApproval: 'never',
      }),
    ],
  });

  // Keep conversation state across turns
  const conversationSession = new OpenAIConversationsSession();

  // Simple CLI
  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: ',
  });

  console.log('\nComposio Tool Router session created.');
  console.log('\nChat started. Type your requests below.');
  console.log("Commands: 'exit', 'quit', or 'q' to end\n");

  try {
    const first = await run(agent, 'What can you help me with?', { session: conversationSession });
    console.log(`Assistant: ${first.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();

  rl.on('line', async (userInput) => {
    const text = userInput.trim();

    if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
      console.log('Goodbye!');
      rl.close();
      process.exit(0);
    }

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

    try {
      const result = await run(agent, text, { session: conversationSession });
      console.log(`\nAssistant: ${result.finalOutput}\n`);
    } catch (e) {
      console.error('Error:', e instanceof Error ? e.message : e, '\n');
    }

    rl.prompt();
  });

  rl.on('close', () => {
    console.log('\nSession ended.');
    process.exit(0);
  });
}

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

Conclusion

This was a starter code for integrating Control d MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Control d.

Key features:

  • Hosted MCP tool integration through Composio's Tool Router
  • SQLite session persistence for conversation history
  • Simple async chat loop for interactive testing
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
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

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

Mastra AI logo

Mastra AI

Use Control d MCP with Mastra AI

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. OpenAI Agents SDK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right 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