Control D logo
AI agent integrationControl D

Control D integration for multiplayer collaboration with AI agents using Claude Code or Codex

One governed connection your whole team and its AI agents can share, with approved actions and human review, so working in Control D never means pasting credentials into a prompt.

Use Control D from Claude Code

Bring Control D context into engineering work while Type keeps app access attached to the teammate and workspace.

Automate Control D with Codex

Let coding agents ask for the right app action, preserve conversation context, and keep humans in the approval loop.

Connect open agent workflows

Use Type as the collaboration layer around OpenClaw and other LLM workflows that need app access.

Security & Identity

What the Control D integration exposes

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 teammates

Connect Control D once, then decide which teammates can use it for threads, automations, skills, 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 Code use Control D?

Yes. Type lets an AI teammate use connected Control D actions from a governed workspace context, so Claude Code work can reference the app without copying credentials into a local prompt.

Can Codex work with Control D through Type?

Yes. Codex can collaborate through Type with app context, skills, and approved actions. The Control D catalog entry includes public integration details and example capabilities where available.

Is this the same as a Control D MCP server?

Type exposes connected app capabilities to AI teammates and coding agents through Type's integration layer. Teams use it when they want shared app access, human review, and teammate-level permissions around agent work.

More security & identity apps for AI teammates