How to integrate Control d MCP with OpenAI Agents SDK

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Control d Logo
open-ai-agents-sdk Logo
divider

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 my account, remove a device by its id, show known access ips for my network, delete a custom dns rule from a profile 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.

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 open-ai-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.

Supported Tools & Triggers

Tools
Delete Device by IDTool to delete a Control-D device.
Delete Profile by IDTool to delete a profile.
Delete Profile Rule by HostnameTool to delete a specific custom rule by hostname from a profile.
Delete Profile Rule by Rule IDTool to delete a specific custom rule by its ID within a profile.
Delete Profile Rule in FolderTool to delete a specific custom rule within a folder.
Delete Profile ScheduleTool to delete a specific schedule within a profile.
List Known Access IPsTool to list known IPs associated with the account.
Get Analytics EndpointsTool to list analytics storage regions and their endpoints.
Get DevicesTool to list all devices associated with the account.
Get Organization DetailsTool to view the authenticated organization's details.
Get ProfilesTool to list all profiles associated with the authenticated account.
Get Profile OptionsTool to get all available profile options.
Get Profile by IDTool to retrieve details of a specific profile by its ID.
Get Profile AnalyticsTool to retrieve analytics data for a specific profile.
Get Profile Analytics LogsTool to list analytics log entries for a given profile.
Get Analytics Log EntryTool to retrieve a specific analytics log entry by its ID.
Get Profile Analytics SummaryTool to fetch a summary of analytics data for a given profile.
Get Profile Analytics Top DomainsTool to fetch top domains accessed within a specific profile.
Get Profile Top ServicesTool to fetch top services accessed within a profile.
Get Profile FiltersTool to list native filters associated with a specific profile.
List External Filters for ProfileTool to list third-party filters for a specific profile.
Get Profile FoldersTool to list rule folders (groups) within a profile.
List Custom Rules for ProfileTool to retrieve custom rules associated with a specific profile.
List Custom Rules in FolderTool to retrieve custom rules in a specific folder of a profile.
Get Custom Rule by Rule IDTool to retrieve details of a specific custom rule by its ID.
Get Specific Rule in FolderTool to retrieve a specific rule within a folder by its ID.
Get Profile SchedulesTool to list schedules associated with a specific profile.
Get Profile ScheduleTool to retrieve a specific schedule by its ID within a profile.
Get Profile ServicesTool to list services associated with a specific profile.
Get Service CategoriesTool to list all service categories.
List Services by CategoryTool to list all services within a specific category.
Get UsersTool to retrieve user account data.
Create DeviceTool to create a new device.
Create ProfileTool to create a new blank profile or clone an existing one.
Create Custom Rules for ProfileTool to create custom rules for a profile.
Create Custom Rules in Profile FolderTool to create custom rules within a specific folder for a profile.
Create Profile ScheduleTool to create a new schedule within a specific profile.
Modify DeviceTool to modify an existing device.
Modify OrganizationTool to modify organization settings and limits.
Update Profile by IDTool to modify an existing profile by ID.
Bulk Update Profile FiltersTool to bulk update filters on a specific profile.
Update External Filters for ProfileTool to update external filters for a specific profile.
Modify Profile FilterTool to modify the enabled state of a specific filter on a profile.
Modify Custom Rules for ProfileTool to modify existing custom rule(s) for a profile.
Update Custom Rule by Rule IDTool to update an existing custom rule by its ID.
Move Profile Rule to FolderTool to move a specific custom rule into a different folder.
Update Profile ScheduleTool to update a specific schedule within a profile.
Modify Service for ProfileTool to modify a specific service rule for a profile.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router 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 Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router 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

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

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

Install dependencies

pip install composio_openai_agents openai-agents python-dotenv

Install the Composio SDK and the OpenAI Agents SDK.

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.

Import dependencies

import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession
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.

Set up the Composio instance

load_dotenv()

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

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())
What's happening:
  • load_dotenv() loads your .env file so OPENAI_API_KEY and COMPOSIO_API_KEY are available as environment variables.
  • Creating a Composio instance using the API Key and OpenAIAgentsProvider class.

Create a Tool Router session

# Create a Control d Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["control_d"]
)

mcp_url = 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.

Configure the agent

# Configure agent with MCP tool
agent = 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(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "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 dict includes the Composio API key for secure authentication with the MCP server.
  • require_approval: 'never' means the agent can execute Control d operations without asking for permission each time, making interactions smoother.

Start chat loop and handle conversation

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
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 Runner.run().
  • The responses are printed to the console, and conversations are saved locally using SQLite.
  • Typing exit, quit, or q cleanly ends the chat.

Complete Code

Here's the complete code to get you started with Control d and open-ai-agents-sdk:

import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession

load_dotenv()

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

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())

# Create Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["control_d"]
)
mcp_url = session.mcp.url

# Configure agent with MCP tool
agent = 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(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())

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.

How to build Control d MCP Agent with another framework

Claude Agent SDK

Claude Agent SDK

Use Control d MCP with Claude Agent SDK

Google ADK

Google ADK

Use Control d MCP with Google ADK

LangChain

LangChain

Use Control d MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Control d MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Control d MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Control d MCP with LlamaIndex

CrewAI

CrewAI

Use Control d MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Control d MCP?

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.

Can I use Tool Router MCP with OpenAI Agents SDK?

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.

Can I manage the permissions and scopes for Control d while using Tool Router?

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.

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

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
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.

Book a call↗Get started for free