Control D logo
ConnectorControl D

Control D integration for Claude and Codex

Create a Control D connection, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.

Use Control D from Claude

Add the Control D connection to a Space that runs Claude, then use it from every channel in that Space.

Use Control D from Codex

Add the Control D connection to a Space that runs Codex, then use it from every channel in that Space.

Use Control D from Sidekick

Connect your own OpenClaw to Sidekick while Type provides the conversations, permissions, connections, skills, and automations.

Security & Identity

What the Control D connector can do

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.

One connection, many Spaces

Connect Control D once, then decide which Spaces can use it in threads, skills, automations, and coding work.

Representative actions

  • Delete Device by 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 unique DNS resolvers. Use GET /devices to retrieve valid device IDs before calling this action.

  • Delete Profile

    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 assigned to one or more devices, the deletion will fail. Use this tool when you need to remove an unused profile from the account. To check if a profile is safe to delete, first verify it has no associated devices using the Get Devices or Get Profile endpoints.

  • Delete Profile Rule by 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 hostname/domain they target (e.g., 'example.com', 'ads.domain.com'). Prerequisites: - Obtain profile_id from GET /profiles endpoint - Obtain rule_id (the hostname/domain) from GET /profiles/{profile_id}/rules endpoint Note: Requires write access to the API (read-only tokens will receive a 403 error).

  • Delete Rule from Folder

    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 profile. Requires valid profile_id, rule_id, and folder_id which can be obtained from: - profile_id: Get Profiles action - folder_id: Get Profile Folders action - rule_id: List Custom Rules in Folder action

  • Delete Profile Schedule

    Tool to delete a specific schedule within a profile. Use after confirming profile_id and schedule_id.

Connection

API and auth details

Control D is an API-first DNS filtering and traffic-redirection service. Public docs describe profiles, endpoints/devices, rules, schedules, analytics, billing, and account operations for scripting DNS policy management, onboarding devices, collecting activity logs, and building custom control panels.

FAQ

Questions people ask before connecting Control D

Can Claude use Control D?

Yes. Add a Control D connection to a Space that runs Claude, then use its approved tools and data from any channel in that Space.

Can Codex work with Control D through Type?

Yes. Add a Control D connection to a Space that runs Codex, then use its approved tools and data from any channel in that Space.

Is this the same as a Control D MCP server?

Not exactly. Type uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.

More security & identity connectors