# How to connect Control D to OpenClaw (paste one key, 54 tools) > Connect Control D to OpenClaw with ClawLink: paste your Control D key once and 54 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/control-d The usual route to Control D access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Control D setup: install one ClawHub skill, connect Control D in the browser, and OpenClaw can call real Control D actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Control D. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Control D** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect control-d # connect Control D (browser OAuth) npx -y @useclawlink/cli actions control-d # list available actions npx -y @useclawlink/cli run control-d --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Control D in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Control D API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Control D, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Control D is connected in the dashboard, that agent calls the same 54 Control D tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Control D MCP for OpenClaw Looking for a Control D MCP server for OpenClaw? ClawLink connects Control D to OpenClaw and exposes 54 Control D tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Control D integration](https://claw-link.dev/hermes/control-d) works the same way. ## What the OpenClaw Control D integration can do 54 Control D tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 54. ### 30 of 54 Control D tools for OpenClaw | Tool | What it does | |---|---| | **Get access** `control_d_get_access` | List up to the latest 50 IP addresses that were used to query against a specific Device | | **Get analytics endpoints** `control_d_get_analytics_endpoints` | List analytics storage regions and their endpoints | | **Get analytics levels** `control_d_get_analytics_levels` | Retrieve available analytics log levels for Control D devices | | **Get billing payments** `control_d_get_billing_payments` | Retrieve billing history of all payments made | | **Get billing products** `control_d_get_billing_products` | Retrieve all products currently activated on the Control D account | | **Get devices** `control_d_get_devices` | Lists all Control D devices (endpoints) associated with the account | | **Get devices types** `control_d_get_devices_types` | List all allowed device types in Control D | | **Get ip** `control_d_get_ip` | Retrieve the current IP address and datacenter information for the API request | | **Get network** `control_d_get_network` | Retrieve network stats on available services in different POPs (Points of Presence) | | **Get organizations members** `control_d_get_organizations_members` | View organization membership | | **Get organizations organization** `control_d_get_organizations_organization` | View the authenticated organization's details | | **Get organizations sub organizations** `control_d_get_organizations_sub_organizations` | View sub-organizations and their details | | **Get profiles** `control_d_get_profiles` | List all profiles associated with the authenticated account | | **Get profiles options** `control_d_get_profiles_options` | Retrieves all available configuration options for DNS profiles in Control D | | **Get profiles profile ID** `control_d_get_profiles_profile_id` | Retrieve details of a specific profile by its ID | | **Get profiles profile ID analytics** `control_d_get_profiles_profile_id_analytics` | Retrieve analytics data for a Control D profile | | **Get profiles profile ID analytics logs** `control_d_get_profiles_profile_id_analytics_logs` | Retrieves DNS query activity logs for a specific Control D profile | | **Get profiles profile ID analytics logs log ID** `control_d_get_profiles_profile_id_analytics_logs_log_id` | Retrieve a specific analytics log entry by its ID | | **Get profiles profile ID analytics summary** `control_d_get_profiles_profile_id_analytics_summary` | Fetch a summary of analytics data for a given profile | | **Get profiles profile ID analytics top domains** `control_d_get_profiles_profile_id_analytics_top_domains` | Fetch top domains accessed within a specific profile | | **Get profiles profile ID analytics top services** `control_d_get_profiles_profile_id_analytics_top_services` | Fetch top services accessed within a profile | | **Get profiles profile ID filters** `control_d_get_profiles_profile_id_filters` | List all native (Control D curated) filters for a profile and their current states | | **Get profiles profile ID filters external** `control_d_get_profiles_profile_id_filters_external` | List third-party filters for a specific profile | | **Get profiles profile ID folders** `control_d_get_profiles_profile_id_folders` | List all rule folders (groups) within a Control D profile | | **Get profiles profile ID rules** `control_d_get_profiles_profile_id_rules` | Retrieve custom DNS rules for a Control D profile | | **Get profiles profile ID rules rule ID folder ID** `control_d_get_profiles_profile_id_rules_rule_id_folder_id` | Retrieve a specific rule within a folder by its ID | | **Get profiles profile ID schedules** `control_d_get_profiles_profile_id_schedules` | List schedules associated with a specific profile | | **Get profiles profile ID schedules schedule ID** `control_d_get_profiles_profile_id_schedules_schedule_id` | Retrieve a specific schedule by its ID within a profile | | **Get profiles profile ID services** `control_d_get_profiles_profile_id_services` | List services associated with a specific profile | | **Get proxies** `control_d_get_proxies` | Retrieve the list of usable proxy locations that traffic can be redirected through | ## Example prompts **Get Access** > Pull the relevant data from Control D, summarize it in plain English, and point out anything that needs attention. **Get Analytics Endpoints** > Pull the relevant data from Control D, summarize it in plain English, and point out anything that needs attention. **Get Analytics Levels** > Pull the relevant data from Control D, summarize it in plain English, and point out anything that needs attention. **Get Billing Payments** > Pull the relevant data from Control D, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Control D working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Control D API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Control D account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Control D. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Control D actions to the runtime in a format your agent can reliably use. | 54 tools for Control D are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Control D to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Control D in the browser, and the 54 tools above work from chat. There is no SDK and no config file, and the Control D key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Control D skill but can't call the tools The ClawHub skill teaches OpenClaw about Control D, but the calls run through the ClawLink plugin and your connected account. Make sure Control D is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Control D from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Control D tools Control D tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Control D call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Control D returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Control D has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Control D integration? Yes. ClawLink is the fastest way to connect OpenClaw to Control D: link your Control D account once in the browser and OpenClaw can call the Control D API through 54 ready-made tools — no custom code or token handling. ### How do I add Control D to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Control D skill from ClawHub, then you click Connect in the dashboard to authorize Control D. OpenClaw calls the tools from the next message — no config files, and the Control D key you paste is stored server-side instead of in your environment. ### How long does it take to connect Control D to OpenClaw? About two minutes. Sign in, click Connect next to Control D in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Control D up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Control D working from chat. ### OpenClaw installed the Control D skill but can't call the tools The ClawHub skill teaches OpenClaw about Control D, but the calls run through the ClawLink plugin and your connected account. Make sure Control D is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [Connect GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty tools](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [OpenClaw SafetyCulture integration](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.