cloudflare-browser-rendering-automation

Cloudflare Browser Rendering Automation via Rube MCP

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "cloudflare-browser-rendering-automation" with this command: npx skills add composiohq/awesome-claude-skills/composiohq-awesome-claude-skills-cloudflare-browser-rendering-automation

Cloudflare Browser Rendering Automation via Rube MCP

Automate Cloudflare Browser Rendering operations through Composio's Cloudflare Browser Rendering toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/cloudflare_browser_rendering

Prerequisites

  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)

  • Active Cloudflare Browser Rendering connection via RUBE_MANAGE_CONNECTIONS with toolkit cloudflare_browser_rendering

  • 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 cloudflare_browser_rendering

  • 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: "Cloudflare Browser Rendering 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 Cloudflare Browser Rendering task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["cloudflare_browser_rendering"] 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 Cloudflare Browser Rendering-specific use case

Connect RUBE_MANAGE_CONNECTIONS with toolkit cloudflare_browser_rendering

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 Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Automation

gmail-automation

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

google-calendar-automation

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

googlesheets-automation

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

telegram-automation

No summary provided by upstream source.

Repository SourceNeeds Review