# Control D — how to use (mcp.ai)

Connect your Control D account and use 54 tools for security and identity straight from your AI agent. Connect with your own API key. Control D is a customizable DNS filtering and traffic redirection platform that allows users to manage internet access, enforce policies, and monitor usage across devices and networks.

## Option A — via MCP (recommended)
Remote MCP endpoint (HTTP, streamable): `https://api.mcp.ai/p_control_d?ms=1787295720000`
Add it as a custom/remote MCP connector in your client (Claude, Cursor, VS Code…), then authenticate when prompted. Once connected, ask the agent to use the server's tools (e.g. `control_d_delete_devices_device_id`).

## Option B — via direct REST API
Base URL: `https://api.mcp.ai/api/control_d`
Auth: `Authorization: Bearer sk_live_…` — create a workspace API key at https://mcp.ai/settings/api-keys
Discover endpoints: `GET https://api.mcp.ai/api/control_d/_endpoints`

### Endpoints
- `POST https://api.mcp.ai/api/control_d/delete/devices/device/id` — Permanently delete a Control-D device/endpoint by its ID. WARNING: This is a destructive operation. Deleting a device will break DNS resolution on any physical gadget configured to use this device's u
  - body: { device_id: string, x_force_org_id?: string }
- `POST https://api.mcp.ai/api/control_d/delete/profiles/profile/id` — Permanently deletes a Control D profile by its unique identifier (PK). IMPORTANT: The profile must be orphaned (not enforced by any device) before it can be deleted. If the profile is currently assign
  - body: { profile_id: string }
- `POST https://api.mcp.ai/api/control_d/delete/profiles/profile/id/rules/rule/id` — Delete a custom DNS rule from a Control D profile by its rule identifier (hostname/domain). This tool removes a DNS filtering rule from the specified profile. Rules in Control D are identified by the 
  - body: { rule_id: string, profile_id: string }
- `POST https://api.mcp.ai/api/control_d/delete/profiles/profile/id/rules/rule/id/folder/id` — Delete a custom DNS rule from a specific folder in a Control D profile. This action permanently removes a custom rule (e.g., block, bypass, spoof, or redirect) from the specified folder within a profi
  - body: { rule_id: string, folder_id: string, profile_id: string }
- `POST https://api.mcp.ai/api/control_d/delete/profiles/profile/id/schedules/schedule/id` — Tool to delete a specific schedule within a profile. Use after confirming profile_id and schedule_id.
  - body: { profile_id: string, schedule_id: string }
- `POST https://api.mcp.ai/api/control_d/get/access` — List up to the latest 50 IP addresses that were used to query against a specific Device (resolver). Use this to retrieve known access IPs associated with a device in your Control D account.
  - body: { device_id: string, X-Force-Org-Id?: string }
- `POST https://api.mcp.ai/api/control_d/get/analytics/endpoints` — Tool to list analytics storage regions and their endpoints. Use after authenticating to retrieve available analytics regions.
- `POST https://api.mcp.ai/api/control_d/get/analytics/levels` — Tool to retrieve available analytics log levels for Control D devices. Use when you need to know what analytics options can be configured on devices (No Analytics, Some Analytics, Full Analytics).
- `POST https://api.mcp.ai/api/control_d/get/billing/payments` — Tool to retrieve billing history of all payments made. Use when you need to access payment records, transaction history, or billing information for the account.
  - body: { X-Force-Org-Id?: string }
- `POST https://api.mcp.ai/api/control_d/get/billing/products` — Retrieve all products currently activated on the Control D account. Use this to view active billing products, subscriptions, and their details.
- `POST https://api.mcp.ai/api/control_d/get/devices` — Lists all Control D devices (endpoints) associated with the account. Each device represents a unique DNS resolver that enforces a Profile (set of filtering rules). Use this to retrieve device inventor
  - body: { device_type?: string, x_force_org_id?: string }
- `POST https://api.mcp.ai/api/control_d/get/devices/types` — List all allowed device types in Control D. Returns categorized device types (OS, Browser, TV, Router) with their available icon identifiers and human-readable labels. Use when you need to display dev
- `POST https://api.mcp.ai/api/control_d/get/ip` — Tool to retrieve the current IP address and datacenter information for the API request. Use when you need to check which IP address is being used or which Control D datacenter is handling requests.
- `POST https://api.mcp.ai/api/control_d/get/network` — Tool to retrieve network stats on available services in different POPs (Points of Presence). Use when you need information about service availability across Control D's network infrastructure.
- `POST https://api.mcp.ai/api/control_d/get/organizations/members` — Tool to view organization membership. Use to retrieve a list of all members in the organization including their email, status, permission levels, and last activity.
- `POST https://api.mcp.ai/api/control_d/get/organizations/organization` — Tool to view the authenticated organization's details. Use after confirming a valid API token.
- `POST https://api.mcp.ai/api/control_d/get/organizations/sub/organizations` — Tool to view sub-organizations and their details. Use when you need to list all sub-organizations under the authenticated organization account.
- `POST https://api.mcp.ai/api/control_d/get/profiles` — Tool to list all profiles associated with the authenticated account. Use when you need an overview of accessible profiles.
  - body: { X-Force-Org-Id?: string }
- `POST https://api.mcp.ai/api/control_d/get/profiles/options` — Retrieves all available configuration options for DNS profiles in Control D. Returns a list of profile options including security filters (Safe Search, AI Malware Filter), TTL settings, block response
  - body: { X-Force-Org-Id?: string }
- `POST https://api.mcp.ai/api/control_d/get/profiles/profile/id` — Tool to retrieve details of a specific profile by its ID. Use when you need full profile details after confirming the profile_id.
  - body: { profile_id: string, X-Force-Org-Id?: string }
- `POST https://api.mcp.ai/api/control_d/get/profiles/profile/id/analytics` — Retrieve analytics data for a Control D profile. Returns DNS query statistics and traffic data for the specified profile. Use profile_id='0' to get analytics for all profiles, or specify a profile ID 
  - body: { profile_id: string }
- `POST https://api.mcp.ai/api/control_d/get/profiles/profile/id/analytics/logs` — Retrieves DNS query activity logs for a specific Control D profile. This tool fetches analytics logs that record DNS queries made through the profile, including details about blocked, allowed, and red
  - body: { to_date?: string, from_date?: string, profile_id: string, X-Force-Org-Id?: string }
- `POST https://api.mcp.ai/api/control_d/get/profiles/profile/id/analytics/logs/log/id` — Tool to retrieve a specific analytics log entry by its ID. Use when you need details of an analytics log for a given profile.
  - body: { log_id: string, profile_id: string, X-Force-Org-Id?: string }
- `POST https://api.mcp.ai/api/control_d/get/profiles/profile/id/analytics/summary` — Tool to fetch a summary of analytics data for a given profile. Use after confirming profile ID and desired date range.
  - body: { to_date?: string, from_date?: string, profile_id: string }
- `POST https://api.mcp.ai/api/control_d/get/profiles/profile/id/analytics/top/domains` — Tool to fetch top domains accessed within a specific profile. Use after confirming profile ID.
  - body: { to_date?: string, from_date?: string, profile_id: string }
- `POST https://api.mcp.ai/api/control_d/get/profiles/profile/id/analytics/top/services` — Tool to fetch top services accessed within a profile. Use after confirming the profile ID and desired date range.
  - body: { to_date?: string, from_date?: string, profile_id: string }
- `POST https://api.mcp.ai/api/control_d/get/profiles/profile/id/filters` — List all native (Control D curated) filters for a profile and their current states. Native filters are hand-curated blocklists maintained by Control D (e.g., 'Ads & Trackers', 'Malware', 'Adult Conten
  - body: { profile_id: string, X-Force-Org-Id?: string }
- `POST https://api.mcp.ai/api/control_d/get/profiles/profile/id/filters/external` — Tool to list third-party filters for a specific profile. Use when you need to retrieve all external filters and their states after confirming the profile ID.
  - body: { profile_id: string, X-Force-Org-Id?: string }
- `POST https://api.mcp.ai/api/control_d/get/profiles/profile/id/folders` — List all rule folders (groups) within a Control D profile. Rule folders are used to organize and group custom DNS rules. Each folder has an action type (BLOCK, BYPASS, SPOOF, or REDIRECT) and contains
  - body: { profile_id: string, x_force_org_id?: string }
- `POST https://api.mcp.ai/api/control_d/get/profiles/profile/id/rules` — Retrieve custom DNS rules for a Control D profile. Returns rules that control domain resolution (BLOCK, BYPASS, SPOOF, or REDIRECT actions). Omit folder_id to list root folder rules, or provide a fold
  - body: { folder_id?: string, profile_id: string, X-Force-Org-Id?: string }
- `POST https://api.mcp.ai/api/control_d/get/profiles/profile/id/rules/rule/id/folder/id` — Tool to retrieve a specific rule within a folder by its ID. Use when you need full details of a custom rule in a profile's folder.
  - body: { rule_id: string, folder_id: string, profile_id: string, X-Force-Org-Id?: string }
- `POST https://api.mcp.ai/api/control_d/get/profiles/profile/id/schedules` — Tool to list schedules associated with a specific profile. Use after confirming the profile ID.
  - body: { profile_id: string, x_force_org_id?: string }
- `POST https://api.mcp.ai/api/control_d/get/profiles/profile/id/schedules/schedule/id` — Tool to retrieve a specific schedule by its ID within a profile. Use when you need details of a profile schedule after confirming the profile_id and schedule_id.
  - body: { profile_id: string, schedule_id: string, X-Force-Org-Id?: string }
- `POST https://api.mcp.ai/api/control_d/get/profiles/profile/id/services` — Tool to list services associated with a specific profile. Use when you need to retrieve all services that have any associated rules after confirming the profile ID.
  - body: { profile_id: string, x_force_org_id?: string }
- `POST https://api.mcp.ai/api/control_d/get/proxies` — Tool to retrieve the list of usable proxy locations that traffic can be redirected through. Use when you need to see available proxy exit locations for routing traffic via transparent proxies.
- `POST https://api.mcp.ai/api/control_d/get/services/categories` — List all available service categories in Control D. Returns categories like audio, video, social, gaming, etc. Each category contains multiple services that can be blocked or allowed. Use the returned
- `POST https://api.mcp.ai/api/control_d/get/services/categories/category` — Retrieves all services within a specific ControlD service category. Use this to discover available services (like Spotify, Netflix, Steam, etc.) that can be configured for DNS filtering or redirection
  - body: { category: string }
- `POST https://api.mcp.ai/api/control_d/get/users` — Retrieve the authenticated user's account information from Control D. This tool returns comprehensive user account data including: - Basic user info (email, status, 2FA settings) - Organization member
- `POST https://api.mcp.ai/api/control_d/post/devices` — Create a new device (DNS endpoint) in Control D. Each device gets unique DNS resolvers that enforce configured profiles. Requires a valid profile_id from GET_PROFILES. Returns DNS resolver URLs (DoH, 
  - body: { desc?: string, icon: string, name: string, stats?: integer, learn_ip?: integer, profile_id: string, restricted?: integer, profile_id2?: string, legacy_ipv4_status?: integer }
- `POST https://api.mcp.ai/api/control_d/post/profiles` — Create a new blank profile or clone an existing one. Profiles define DNS filtering rules, services, and settings that can be applied to devices. Use this to provision a new profile before assigning ru
  - body: { name: string, X-Force-Org-Id?: string, clone_profile_id?: string }
- `POST https://api.mcp.ai/api/control_d/post/profiles/profile/id/rules` — Create custom DNS rules for a profile to control domain resolution. Use this to block ads/trackers, bypass filtering for specific domains, spoof DNS responses with custom IPs, or redirect traffic thro
  - body: { do: integer, via?: string, group?: integer, status?: integer, via_v6?: string, hostnames: string[], profile_id: string, X-Force-Org-Id?: string }
- `POST https://api.mcp.ai/api/control_d/post/profiles/profile/id/rules/folder/id` — Tool to create custom rules within a specific folder for a profile. Use after confirming the profile and folder IDs and preparing rule definitions.
  - body: { rules: object[], folder_id: string, profile_id: string, X-Force-Org-Id?: string }
- `POST https://api.mcp.ai/api/control_d/post/profiles/profile/id/schedules` — Create a new time-based schedule within a Control D profile. Schedules allow automatic enforcement of profile rules during specified time windows. Use this to set up recurring time periods (e.g., work
  - body: { schedule: object, profile_id: string, X-Force-Org-Id?: string }
- `POST https://api.mcp.ai/api/control_d/put/devices/device/id` — Modify an existing Control D device's settings. Use this tool to update device properties such as name, associated profiles, analytics level, IP learning, restrictions, DDNS settings, and status. At l
  - body: { desc?: string, name?: string, stats?: integer, status?: integer, bump_tls?: integer, learn_ip?: integer, device_id: string, profile_id?: string, restricted?: integer, ddns_status?: integer, profile_id2?: string, ddns_ext_host?: string, ddns_subdomain?: string, x_force_org_id?: string, ddns_ext_status?: integer, legacy_ipv4_status?: integer, ctrld_custom_config?: string }
- `POST https://api.mcp.ai/api/control_d/put/organizations` — Modify organization settings such as name, contact details, website, and device limits. Use this to update organization metadata or change billing-related limits (max_users, max_routers). Note: Changi
  - body: { name?: string, address?: string, website?: string, max_users?: integer, twofa_req?: integer, max_routers?: integer, contact_name?: string, contact_email?: string, contact_phone?: string, X-Force-Org-Id?: string, parent_profile?: string, stats_endpoint?: string }
- `POST https://api.mcp.ai/api/control_d/put/profiles/profile/id` — Modify an existing profile by its ID. Use this to update profile properties such as the display name, deactivation timestamp, or lock status. Requires at least one modifiable field (name, disable_ttl,
  - body: { name?: string, password?: string, profile_id: string, disable_ttl?: integer, lock_status?: integer, lock_message?: string, X-Force-Org-Id?: string }
- `POST https://api.mcp.ai/api/control_d/put/profiles/profile/id/filters` — Tool to bulk update filters on a specific profile. Use when you need to enable or disable multiple filters at once. Provide a list of filter IDs with desired states.
  - body: { filters: object[], profile_id: string, x_force_org_id?: string }
- `POST https://api.mcp.ai/api/control_d/put/profiles/profile/id/filters/external` — Tool to update external filters for a specific profile. Use when toggling third-party filters after listing them.
  - body: { filters: object[], profile_id: string, X-Force-Org-Id?: string }
- `POST https://api.mcp.ai/api/control_d/put/profiles/profile/id/filters/filter/filter` — Modify the enabled state of a specific native filter on a profile. Use this tool to enable or disable individual content filters like 'ads', 'malware', 'social', etc. on a specific profile. The filter
  - body: { filter: string, status: integer, profile_id: string, x_force_org_id?: string }
- `POST https://api.mcp.ai/api/control_d/put/profiles/profile/id/rules` — Modify an existing custom DNS rule for a profile in Control D. Use this to update rule properties such as action type (block/bypass/spoof/redirect), status (enabled/disabled), target hostnames, and re
  - body: { do: integer, via?: string, group?: integer, status: integer, via_v6?: string, hostnames: string[], profile_id: string, X-Force-Org-Id?: string }
- `POST https://api.mcp.ai/api/control_d/put/profiles/profile/id/rules/rule/id` — Tool to update an existing custom rule by its ID. Use when modifying details like name, description, severity, or enabled status for a specific rule.
  - body: { name?: string, enabled?: boolean, rule_id: string, severity?: integer, profile_id: string, description?: string, X-Force-Org-Id?: string }
- `POST https://api.mcp.ai/api/control_d/put/profiles/profile/id/rules/rule/id/folder/id` — Tool to move a specific custom rule into a different folder. Use after confirming profile_id, rule_id, and folder_id.
  - body: { rule_id: string, folder_id: string, profile_id: string }
- `POST https://api.mcp.ai/api/control_d/put/profiles/profile/id/schedules/schedule/id` — Tool to update a specific schedule within a profile. Use when you need to modify schedule details after confirming profile_id and schedule_id.
  - body: { schedule: object, profile_id: string, schedule_id: string, X-Force-Org-Id?: string }
- `POST https://api.mcp.ai/api/control_d/put/profiles/profile/id/services/service` — Tool to modify a specific service rule for a profile. Use when you need to update blocking, bypassing, spoofing, or proxy-redirect settings after reviewing existing rules.
  - body: { do: integer, via?: string, status: integer, via_v6?: string, service: string, profile_id: string }

## Example prompts
- "What can I do in Control D?"
- "Show me a summary of my Control D account"

## More
- Page: https://mcp.ai/control_d
- Agent spec (llms.txt): https://mcp.ai/control_d/llms.txt
- Postman collection: https://mcp.ai/control_d/postman.json