Parseur Automation

What This Skill Does

This skill automates Parseur operations using Composio's Parseur toolkit through Rube MCP. It is designed for users who need to manage and execute Parseur tasks efficiently. The skill ensures proper connection and schema compliance for seamless automation.

When to Use

Automate Parseur data extraction workflowsDynamically discover and execute Parseur toolsManage active Parseur connections via RubeVerify connection status before task executionAdapt to changing tool schemas automaticallyExecute multiple Parseur tools in one session

Key Features

Integrates with Rube MCP for tool accessUses RUBE_SEARCH_TOOLS for dynamic tool discoveryManages Parseur connections via RUBE_MANAGE_CONNECTIONSSupports RUBE_MULTI_EXECUTE_TOOL for workflow executionProvides toolkit documentation for referenceRequires active Parseur connection for operation

Manual Installation

Manual installationView Full Skill ContentThe complete markdown content that gets installedParseur Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/parseur

Prerequisites

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

Step 2: Check Connection

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

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

Toolkit docs: composio.dev/toolkits/parseur