Control D Automation

What This Skill Does

This skill automates Control D operations through Composio's Control D toolkit via Rube MCP. It is designed for users who want to programmatically manage their Control D configurations. The skill supports tool discovery, connection management, and tool execution.

When to Use

• Discover available Control D tools.
• Check the status of the Control D connection.
• Execute Control D tools with specific arguments.
• Automate network configuration changes.
• Manage custom DNS settings programmatically.
• Integrate Control D with other automation workflows.

Key Features

• Uses Rube MCP for tool discovery and execution.
• Requires an active Control D connection.
• Employs RUBE_SEARCH_TOOLS to find available tools.
• Uses RUBE_MANAGE_CONNECTIONS to manage connections.
• Executes tools via RUBE_MULTI_EXECUTE_TOOL.
• Provides a structured workflow for Control D automation.

Manual Installation

Automate Control D operations through Composio's Control D toolkit via Rube MCP. Toolkit docs: composio.dev/toolkits/control_d

Prerequisites

• Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
• Active Control D connection via RUBE_MANAGE_CONNECTIONS with toolkit control_d
• Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

• Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration.
• No API keys needed — just add the endpoint and it works.
• Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
• Call RUBE_MANAGE_CONNECTIONS with toolkit control_d
• If connection is not ACTIVE, follow the returned auth link to complete setup
• Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS queries: [{use_case: "Control D operations", known_fields: ""}] session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS queries: [{use_case: "your specific Control D task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["control_d"] session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/ schema-compliant args from search results /} }] memory: {} session_id: "your_session_id"

Known Pitfalls

• Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools Schema compliance: Use exact field names and types from the search results Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
• Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Automate Control D operations through Composio's Control D toolkit via Rube MCP. Toolkit docs: composio.dev/toolkits/control_d