How to integrate Control d MCP with Claude Code

GET STARTED FOR FREE
Framework Integration Gradient
Control d Logo
Claude Code Logo
divider

Introduction

Manage your Control d directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Rube - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Why Rube?

Rube is a universal MCP server with access to 850+ SaaS apps. It ensures just-in-time tool loading so Claude can access the tools it needs, a remote workbench for programmatic tool calling and handling large tool responses out of the LLM context window, ensuring the LLM context window remains clean.

Connect Control d to Claude Code with Rube

1. Get the MCP URL

Copy and paste the below command in Claude Code to add Rube MCP.

Terminal

2. Authenticate Rube

Run /mcp to view Rube

bash
/mcp
Run /mcp to view Rube in Claude Code
Click on Rube to authenticate
Authentication flow complete

3. Ensure it's connected

Run /mcp again to verify the connection. Now, do whatever you want with Claude Code and Control d.

Rube connected successfully

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

Connecting Control d via Tool Router

Tool Router is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Control d) for even more tool search precision. It's secure and reliable.

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:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Control d account
  • Basic knowledge of Python or TypeScript

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)

Install Composio library

pip install composio-core python-dotenv

Install the Composio Python library to create MCP sessions.

  • composio-core provides the core Composio functionality
  • python-dotenv loads environment variables from your .env file

Generate Composio MCP URL

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

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

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["control_d"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http control_d-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Create a script to generate a Composio MCP URL for Control d. This URL will be used to connect Claude Code to Control d.

What's happening:
  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Control d
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it

Run the script and copy the MCP URL

python generate_mcp_url.py

Run your Python script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output

Add Control d MCP to Claude Code

bash
claude mcp add --transport http control_d-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (control_d-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

Verify the installation

bash
claude mcp list

Check that your Control d MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your control_d-composio entry in the list
  • This confirms that Claude Code can now access Control d tools

If everything is wired up, you should see your control_d-composio entry listed:

Claude Code MCP list showing the toolkit MCP server

Authenticate Control d

The first time you try to use Control d tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Control d
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Control d authorization flow
  • Return to the terminal and start using Control d through Claude Code

Once authenticated, you can ask Claude Code to perform Control d operations in natural language. For example:

  • "List all devices connected to my account"
  • "Remove a device by its ID"
  • "Show known access IPs for my network"

Complete Code

Here's the complete code to get you started with Control d and Claude Code:

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

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

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["control_d"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http control_d-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Conclusion

You've successfully integrated Control d with Claude Code using Composio's MCP server. Now you can interact with Control d directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Control d operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Control d operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

How to build Control d MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Control d MCP with OpenAI Agents SDK

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 Claude Code?

Yes, you can. Claude Code 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
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.

Book a call↗Get started for free