What is ip2proxy-automation?

A Composio skill to automate Ip2proxy operations through Rube MCP, prioritizing tool discovery first.

No. Setup requires adding the MCP server; authentication is handled via the Rube MCP flow.

Why must I call RUBE_SEARCH_TOOLS first?

Tool schemas change; you must fetch current slugs and argument names before execution.

ip2proxy-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/ip2proxy-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Ip2proxy Automation via Rube MCP

Automate Ip2proxy operations through Composio's Ip2proxy toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/ip2proxy

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Ip2proxy connection via RUBE_MANAGE_CONNECTIONS with toolkit ip2proxy
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 ip2proxy
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: "Ip2proxy 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 Ip2proxy task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["ip2proxy"]
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

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Ip2proxy-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `ip2proxy`
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/ip2proxy-automation/SKILL.mdView on GitHub

Overview

Automates Ip2proxy operations through Composio's Ip2proxy toolkit using Rube MCP. It emphasizes discovering current tool schemas first to prevent hardcoding slugs or arguments and to stay aligned with evolving endpoints.

How This Skill Works

You must have Rube MCP connected and an active Ip2proxy connection via the ip2proxy toolkit. Then discover available tools with RUBE_SEARCH_TOOLS, confirm a session, verify the connection status (ACTIVE), and execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the provided memory and session_id.

When to Use It

Starting a new Ip2proxy workflow and need current tool schemas
Upgrading to a new Ip2proxy tool version with updated fields
Validating an ACTIVE connection before running any workflow
Executing a batch of Ip2proxy operations with multiple tools
Reusing a session for a multi-step Ip2proxy task to avoid repeats

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client and run RUBE_SEARCH_TOOLS to fetch current Ip2proxy tool schemas.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["ip2proxy"] and verify the session shows ACTIVE.
Step 3: Execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, exact args, memory: {}, and the current session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS to fetch current schemas before any run
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the search results
Include a memory object in RUBE_MULTI_EXECUTE_TOOL calls (even if empty)
Reuse session IDs within a workflow; generate new ones for new workflows

Example Use Cases

Discover tools for Ip2proxy, connect, and perform a single proxy lookup
Batch verify multiple IPs against Ip2proxy using RUBE_MULTI_EXECUTE_TOOL
Update a workflow after RUBE_SEARCH_TOOLS reveals new parameters
Reconnect after a period of inactivity and resume with ACTIVE status
Bulk run with RUBE_REMOTE_WORKBENCH to orchestrate several Ip2proxy tasks

Frequently Asked Questions

Add this skill to your agents