graphhopper-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/graphhopper-automation --openclawGraphhopper Automation via Rube MCP
Automate Graphhopper operations through Composio's Graphhopper toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/graphhopper
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Graphhopper connection via
RUBE_MANAGE_CONNECTIONSwith toolkitgraphhopper - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitgraphhopper - 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: "Graphhopper 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 Graphhopper task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["graphhopper"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Graphhopper-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit graphhopper |
| 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/graphhopper-automation/SKILL.mdView on GitHub Overview
Automate Graphhopper operations using Composio's Graphhopper toolkit through Rube MCP. The workflow emphasizes discovering current tool schemas first with RUBE_SEARCH_TOOLS to avoid brittle automation. It covers setup, connection management, and executing tools safely within a session.
How This Skill Works
The automation starts by discovering available tools with RUBE_SEARCH_TOOLS, then establishes or validates a Graphhopper connection via RUBE_MANAGE_CONNECTIONS, and finally executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL. Each execution must include a memory object and use a valid session, reusing sessions when appropriate. Always reference the current tool schemas for argument names and types.
When to Use It
- When you need to automate repetitive Graphhopper operations.
- When tool schemas change and you must fetch current slugs using RUBE_SEARCH_TOOLS.
- When you want to validate and reuse existing sessions across a workflow.
- When performing bulk or batch Graphhopper tasks across multiple regions.
- When integrating Graphhopper tasks into Composio workflows and dashboards.
Quick Start
- Step 1: Add the Rube MCP endpoint as an MCP server (https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS.
- Step 2: Use RUBE_SEARCH_TOOLS to discover available Graphhopper tools for your use case.
- Step 3: Manage the connection for the graphhopper toolkit with RUBE_MANAGE_CONNECTIONS and execute a tool with RUBE_MULTI_EXECUTE_TOOL using a session_id and memory.
Best Practices
- Always call 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 rather than hardcoding.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow and watch for pagination tokens.
Example Use Cases
- Automate a routing calculation and isochrone generation for daily reports.
- Bulk update multiple Graphhopper configurations in a single run.
- Fetch current tool slugs and execute a sequence of tasks with dynamic inputs.
- Run cross region graphhopper tools in batch and aggregate results.
- Resume a failed workflow by reusing the existing session_id.
