OpenClaw is the fastest growing agent harness out there, which can work 24/7 to automate almost any kind of tasks. However, its capabilities are limited to the tools it has access to. Composio allows your OpenClaw to access Control d with authentication management handled for you. You can execute actions on Control d via your favorite OpenClaw interface (Telegram, WhatsApp, TUI, etc), whichever you prefer.
Table of Contents
Connect Control d without Auth hassles
We manage OAuth, API Key, token refresh, and scopes, you just build.
Try for FreeIntroduction
Also integrate Control d with
Why use Composio?
Apart from a managed and hosted MCP server, you will get:
- Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
- Handling Large tool responses out of LLM context to minimize context rot.
- Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.
How to install Control d with OpenClaw
Using Composio API Key and Setup Prompt
- Go to dashboard.composio.dev
- Copy the setup prompt
- Run it in your OpenClaw chat interface.
- Authenticate Control d from the dashboard
- Go back to your OpenClaw interface and start asking questions.
Using OpenClaw/Composio Plugin
1. Install OpenClaw Composio plugin
2. Copy the API Key from dashboard.composio.dev
3. Setup OpenClaw Config
4. Restart OpenClaw
5. Go to your chat interface and start asking questions.
6. When prompted, authenticate the app and you're all set.
How It Works
The plugin connects to Composio's MCP server at https://connect.composio.dev/mcp and registers all available tools directly into the OpenClaw agent. Tools are called by name — no extra search or execute steps needed.
If a tool returns an auth error, the agent will prompt you to connect that toolkit at dashboard.composio.dev.
Configuration
| Option | Description | Default |
|---|---|---|
enabled | Enable or disable the plugin | true |
consumerKey | Your Composio consumer key (ck_...) | — |
mcpUrl | MCP server URL (advanced) | https://connect.composio.dev/mcp |
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.
Supported Tools & Triggers
Tools
Conclusion
You've successfully integrated Control d with OpenClaw using Composio plugin. Now interact with Control d directly from your terminal, Web UI, or any messenger app using natural language commands.
Key benefits of this setup:
- Seamless integration across TUI, Web UIs, and Messenger apps like Telegram, WhatsApp, Slack, etc.
- Natural language commands for Control d operations
- Managed authentication through Composio
- Access to 20,000+ tools across 1000+ apps for cross-app workflows
- Programmatic tool calling for complex tool chaining
Next steps:
- Try asking OpenClaw to perform various Control d operations
- Explore cross-app workflows by connecting more toolkits like Calendar, Slack, Notion, etc.
- Build complex automation scripts that leverage OpenClaw's 24/7 running capabilities
How to build Control d MCP Agent with another framework
Explore Other Toolkits
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 OpenClaw?
Yes, you can. OpenClaw 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.
