PromptShop

Geoapify Automation

This skill automates Geoapify operations using Composio's toolkit through Rube MCP. It allows users to programmatically access geocoding, reverse geocoding, .

Install

npx promptshop add geoapify-automation

Details

What This Skill Does

This skill automates Geoapify operations using Composio's toolkit through Rube MCP. It allows users to programmatically access geocoding, reverse geocoding, and other location-based services. It is designed for developers who need to integrate mapping and location data into their applications.

When to Use

  • Geocode addresses to coordinates.
  • Reverse geocode coordinates to addresses.
  • Find nearby places of interest.
  • Calculate routes and distances.
  • Integrate mapping into applications.

Key Features

  • Automates Geoapify via Rube MCP.
  • Requires Rube MCP and active Geoapify connection.
  • Discovers tools using RUBE_SEARCH_TOOLS.
  • Checks connection with RUBE_MANAGE_CONNECTIONS.
  • Executes tools using RUBE_MULTI_EXECUTE_TOOL.
  • Requires schema compliance and connection verification.

Manual Installation

Geoapify Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/geoapify

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["geoapify"] 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 Geoapify-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit geoapify
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

Geoapify Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/geoapify

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS queries: [{use_case: "your specific Geoapify task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["geoapify"] 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 Geoapify-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit geoapify
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