$ ~/registry/skill/composiohq-composio-skills-route4me-automation

SKILL

route4me-automation

Automate Route4me tasks via Rube MCP with tool discovery first.

Stars

★ 73,665

Source

GitHub

Updated

2026-08-28

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 73.7k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "route4me-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/route4me-automation/SKILL.md
2. Save it as ~/.claude/skills/route4me-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// use cases

Integrate Route4me automation into a workflow

When developers integrate Route4me into an MCP workflow, they can search for the current tool schema first, verify the connection, and then execute the right operation to avoid failures caused by schema changes.

Validate connection and arguments before execution

Before running Route4me-related tasks, DevOps or workflow builders can confirm that the route4me connection is ACTIVE and execute tools using the exact fields returned by tool discovery.

Handle multi-step Route4me operations

For tasks that require multiple calls, users can reuse the same session, discover tools first, execute them next, and continue with pagination or follow-up steps based on the responses.

// docs

AI summary

The documentation explains how to automate Route4me tasks through Composio's Route4me toolkit via Rube MCP. It covers prerequisites, setup, tool discovery, and execution flow. A key requirement is to always call `RUBE_SEARCH_TOOLS` first to get the latest schemas, then verify the route4me connection is ACTIVE before using `RUBE_MULTI_EXECUTE_TOOL`. It also highlights session reuse, the required `memory` parameter, and pagination handling.

Show full docs ▾

Route4me Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/route4me

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["route4me"]
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 Route4me-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `route4me`
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

// FAQ

What does this skill do?

It uses Rube MCP to access Composio's Route4me toolkit for automating Route4me-related operations. The documentation specifically emphasizes searching for the current tools and schemas before execution.

What are the prerequisites?

You need Rube MCP connected first, with `RUBE_SEARCH_TOOLS` available. You also need to configure and activate the route4me connection through `RUBE_MANAGE_CONNECTIONS`, and its status should be ACTIVE.

How is this different from hardcoding tool arguments?

The docs say tool schemas can change, so you should not hardcode tool slugs or arguments. The recommended pattern is to call `RUBE_SEARCH_TOOLS` first and then execute against the latest returned schema.

Automate Mapbox tasks through Rube MCP for mapping and workflow operations.

ComposioGet→

$ loading_