nextdns-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/nextdns-automation --openclawNextdns Automation via Rube MCP
Automate Nextdns operations through Composio's Nextdns toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/nextdns
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Nextdns connection via
RUBE_MANAGE_CONNECTIONSwith toolkitnextdns - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitnextdns - 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: "Nextdns 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 Nextdns task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["nextdns"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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
| Operation | Approach |
|---|---|
| Find tools | RUBE_SEARCH_TOOLS with Nextdns-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit nextdns |
| Execute | RUBE_MULTI_EXECUTE_TOOL with discovered tool slugs |
| Bulk ops | RUBE_REMOTE_WORKBENCH with run_composio_tool() |
| Full schema | RUBE_GET_TOOL_SCHEMAS for tools with schemaRef |
Powered by Composio
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/nextdns-automation/SKILL.mdView on GitHub Overview
Automate Nextdns operations through Composio's Nextdns toolkit using Rube MCP. The workflow relies on discovering current tool schemas with RUBE_SEARCH_TOOLS before execution, ensuring slugs and input fields stay up-to-date. This enables repeatable, schema-driven automation for Nextdns setup, management, and tasks.
How This Skill Works
The skill first discovers available Nextdns tools via RUBE_SEARCH_TOOLS. It then checks the Nextdns connection with RUBE_MANAGE_CONNECTIONS and executes the chosen tool using RUBE_MULTI_EXECUTE_TOOL, passing a memory object and session_id. This pattern ensures correct tool selection, active connections, and traceable workflows.
When to Use It
- When you need to automate routine Nextdns tasks end-to-end (discover tools, connect, run).
- When tool schemas change, and you must fetch current slugs and inputs before automation.
- When establishing a Nextdns workflow, ensure the connection is ACTIVE before execution.
- When performing multiple Nextdns actions in a single workflow, reuse the same session_id.
- When handling complex or bulk Nextdns operations, pass a memory object and orchestrate with RUBE_MULTI_EXECUTE_TOOL.
Quick Start
- Step 1: Add the MCP server at https://rube.app/mcp and confirm RUBE_SEARCH_TOOLS responds.
- Step 2: Connect to Nextdns via RUBE_MANAGE_CONNECTIONS with toolkit 'nextdns' and verify ACTIVE.
- Step 3: Discover available tools with RUBE_SEARCH_TOOLS, then execute a selected tool using RUBE_MULTI_EXECUTE_TOOL with a memory object and session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools.
- Use exact field names and types from search results; avoid hardcoding slugs.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow and generate new ones for new workflows.
Example Use Cases
- Discover available Nextdns operations with RUBE_SEARCH_TOOLS and run a specific task using the returned slug.
- Set up the Nextdns connection via RUBE_MANAGE_CONNECTIONS, then execute a health-check or configuration task with RUBE_MULTI_EXECUTE_TOOL.
- Create a multi-step Nextdns workflow that reuses a session_id across steps and uses memory to share state.
- If tool schemas change, re-run RUBE_SEARCH_TOOLS to retrieve the latest slugs before continuing.
- Perform bulk Nextdns operations by sequencing multiple tool executions through RUBE_MULTI_EXECUTE_TOOL with a shared session and memory.
