What is ip2location-automation?

A workflow that automates Ip2location operations through the Composio Ip2location toolkit via Rube MCP.

What prerequisites are required?

A connected Rube MCP with RUBE_SEARCH_TOOLS available, an active Ip2location connection managed via RUBE_MANAGE_CONNECTIONS drawing on the ip2location toolkit, and a habit of always searching tools first.

Why should I always search tools first?

Tool schemas change frequently. Fetch current slugs and input schemas before coding or hardcoding any values to avoid broken workflows.

ip2location-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Ip2location Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/ip2location

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["ip2location"]
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 Ip2location-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `ip2location`
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/ip2location-automation/SKILL.md

View on GitHub

Overview

Ip2location-automation lets you orchestrate Ip2location operations through Composio's toolkit via Rube MCP. It relies on a connected Rube MCP with RUBE_SEARCH_TOOLS and an active Ip2location connection managed with the ip2location toolkit. Always fetch current tool schemas before running workflows to avoid broken integrations.

How This Skill Works

Discover available Ip2location tools with RUBE_SEARCH_TOOLS, then verify the Ip2location connection with RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL, passing the discovered tool slug, exact input fields, memory, and a session_id to maintain workflow state.

When to Use It

When you need to automate large-scale Ip2location lookups across many IPs.
When integrating Ip2location tasks into a CI/CD or automated pipeline to avoid manual steps.
When performing bulk geolocation enrichment for a customer dataset.
When validating new Ip2location tool schemas after an update or change.
When you want to reuse a session across a sequence of Ip2location operations for speed and continuity.

Quick Start

Step 1: Ensure Rube MCP is added (https://rube.app/mcp) and RUBE_SEARCH_TOOLS responds.
Step 2: Discover available Ip2location tools with RUBE_SEARCH_TOOLS and pick a tool_slug.
Step 3: Check the connection with RUBE_MANAGE_CONNECTIONS and run the tool with RUBE_MULTI_EXECUTE_TOOL using memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before attempting to run any workflow to get current tool slugs and schemas.
Verify the Ip2location connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before executing tools.
Use exact field names and types from the discovered tool schema—do not improvise.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow; create new sessions only for distinct workflows and watch for pagination as needed.

Example Use Cases

Automate geolocation for a list of IPs by discovering the Ip2location tool and executing it in a batch.
Test a newly updated Ip2location tool schema after a RUBE_SEARCH_TOOLS refresh and adjust inputs accordingly.
Bulk enrich a customer table with location data and store results in a data warehouse.
Run a nightly Ip2location data quality check across IP ranges and alert on anomalies.
Orchestrate a full workflow: connect to Ip2location, discover tools, execute, and persist results.

Frequently Asked Questions

Add this skill to your agents