PromptShop

Ip2location Automation

It allows users to programmatically access IP geolocation data.

Install

npx promptshop add ip2location-automation

Details

What This Skill Does

This skill automates Ip2location operations through Composio's Ip2location toolkit via Rube MCP. It allows users to programmatically access IP geolocation data. It is designed for developers and security engineers who need to integrate IP geolocation into their applications.

When to Use

Automate IP address geolocation lookupsIntegrate geolocation into security systemsBatch process IP address dataIdentify user locationsCustomize content based on locationDetect fraudulent activity

Key Features

Connects to Ip2location via Rube MCPDiscovers available Ip2location toolsExecutes Ip2location tools with schema validationManages Ip2location connectionsProvides error handling and connection status checksSupports dynamic tool discovery

Manual Installation

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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Ip2location-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit ip2location
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef

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

Toolkit docs: composio.dev/toolkits/ip2location