Do I need an active Ipinfo IO account?

Yes, you must have an active connection via the ipinfo_io toolkit and proper authorization per RUBE_MANAGE_CONNECTIONS.

What happens if tool schemas change?

Always call RUBE_SEARCH_TOOLS first; do not hardcode slugs or arguments.

How do I ensure data persists across steps?

Provide a memory object with RUBE_MULTI_EXECUTE_TOOL and reuse session IDs to maintain continuity.

ipinfo-io-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Ipinfo IO Automation via Rube MCP

Automate Ipinfo IO operations through Composio's Ipinfo IO toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/ipinfo_io

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["ipinfo_io"]
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 Ipinfo IO-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `ipinfo_io`
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/ipinfo-io-automation/SKILL.mdView on GitHub

Overview

Automate Ipinfo IO operations through Composio's Ipinfo IO toolkit using Rube MCP. This skill streamlines discovering current tool schemas, managing Ipinfo IO connections, and executing tools in orchestrated workflows. It helps teams scale IP data tasks with reliable, schema-aware automation.

How This Skill Works

First, verify RUBE_SEARCH_TOOLS is available to fetch current Ipinfo IO tool schemas. Next, ensure an ACTIVE Ipinfo IO connection via RUBE_MANAGE_CONNECTIONS for the ipinfo_io toolkit. Finally, run discovered tools with RUBE_MULTI_EXECUTE_TOOL, supplying the exact memory object and a session_id; always reference up-to-date schemas to avoid failures.

When to Use It

You need geolocation or ASN data for a single IP using Ipinfo IO.
You want to validate multiple IPs and collect structured Ipinfo IO details in one workflow.
You must reuse a session across related Ipinfo IO tasks for consistency.
Tool schemas change often, so you want to fetch current tool slugs before running.
You are deploying batch IP data tasks and require reliable connection status checks.

Quick Start

Step 1: Configure Rube MCP (add https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS responds.
Step 2: Connect to Ipinfo IO with RUBE_MANAGE_CONNECTIONS toolkits: ["ipinfo_io"] and complete auth if required.
Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a chosen tool via RUBE_MULTI_EXECUTE_TOOL using memory and a session ID.

Best Practices

Always run RUBE_SEARCH_TOOLS first to get current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results to ensure schema compliance.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs where appropriate, and generate a new session for new workflows.

Example Use Cases

Discover Ipinfo IO tools for geolocation and run a single API call for IP 8.8.8.8.
Process a list of IPs to fetch ASN and organization data in a single session.
Bulk IP detail extraction with memory persistence across steps.
Authenticate and create a workflow that runs multiple Ipinfo IO tasks in sequence.
Handle tool discovery pagination and continue fetching until all results are retrieved.

Frequently Asked Questions

Add this skill to your agents