Ngrok Automation

What This Skill Does

• The Ngrok Automation skill allows users to automate Ngrok operations through Composio's Ngrok toolkit via Rube MCP.
• It is designed for developers and system administrators who need to programmatically manage Ngrok tunnels and configurations.
• This skill streamlines the process of setting up and managing Ngrok connections.

When to Use

• Automatically create Ngrok tunnels.
• Manage Ngrok configurations programmatically.
• Dynamically update tunnel settings.
• Integrate Ngrok into CI/CD pipelines.
• Automate secure access to local development servers.
• Remotely debug applications via Ngrok.

Key Features

• Automates Ngrok operations via Rube MCP.
• Uses Composio's Ngrok toolkit.
• Requires an active Ngrok connection.
• Discovers available tools using RUBE_SEARCH_TOOLS.
• Checks connection status with RUBE_MANAGE_CONNECTIONS.
• Executes tools using RUBE_MULTI_EXECUTE_TOOL.

Manual Installation

Ngrok Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/ngrok

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["ngrok"] 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