What is Parseur Automation via Rube MCP?

A workflow to automate Parseur operations using Composio's Rube MCP toolkit; it emphasizes discovering current tool schemas before running tasks.

No API keys are needed — just add the MCP server endpoint and connect.

What if tool schemas change?

Always call RUBE_SEARCH_TOOLS first to fetch current slugs and schemas before executing tools, to avoid hardcoding.

parseur-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/parseur-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Parseur 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

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Parseur-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `parseur`
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/parseur-automation/SKILL.mdView on GitHub

Overview

Automate Parseur operations through Composio's Parseur toolkit via Rube MCP. This skill streamlines repetitive parsing tasks by discovering current tool schemas first, ensuring compatibility before execution.

How This Skill Works

The workflow starts by discovering available Parseur tools with RUBE_SEARCH_TOOLS, then verifies an ACTIVE Parseur connection via RUBE_MANAGE_CONNECTIONS. Once ready, tools are executed with RUBE_MULTI_EXECUTE_TOOL using the discovered tool slug and schema-compliant arguments; always include memory and reuse sessions.

When to Use It

You need to automate a recurring Parseur parsing task (invoices, emails, or receipts) using the latest tool schemas.
You want to ensure tool slugs and arguments stay current by always re-searching tool schemas before running workflows.
You are integrating Parseur tasks into a larger automation pipeline and need to verify connection status first.
You are performing bulk Parseur operations in a single session with multiple tool executions.
You need to troubleshoot or extend an existing Parseur workflow by re-fetching tool schemas when changes occur.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["parseur"] and complete the auth flow until status is ACTIVE.
Step 3: Run the Core Workflow: use RUBE_SEARCH_TOOLS to find a Parseur tool, then execute it with RUBE_MULTI_EXECUTE_TOOL using a memory object and your session_id.

Best Practices

Always search tool schemas first to pick up current tool slugs and arguments.
Confirm the Parseur connection is ACTIVE before executing any tools.
Use exact field names and types from the search results in your tool calls.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and handle pagination tokens when present.

Example Use Cases

Parse a new invoice by discovering the appropriate tool with RUBE_SEARCH_TOOLS, connecting to Parseur, and executing the tool with the required fields.
Extract customer contact data from incoming emails by locating the correct Parseur tool and running it with exact schema fields.
Batch process multiple receipts in a single session using RUBE_MULTI_EXECUTE_TOOL, reusing the same session_id.
Update an existing workflow after tool schemas change by re-running RUBE_SEARCH_TOOLS before execution.
Handle large tool-result sets by paging through tool schemas and results with RUBE_GET_TOOL_SCHEMAS and RUBE_SEARCH_TOOLS.

Frequently Asked Questions

Add this skill to your agents