$ ~/registry/skill/composiohq-composio-skills-parseur-automation

SKILL

parseur-automation

Automate Parseur workflows through Rube MCP with tool discovery and execution.

Stars

★ 73,862

Source

GitHub

Updated

2026-08-29

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 73.9k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "parseur-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/parseur-automation/SKILL.md
2. Save it as ~/.claude/skills/parseur-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// use cases

Dynamic tool discovery for Parseur workflows

Developers or automation users can search for currently available tools and parameter schemas before building a Parseur workflow, reducing failures caused by changing interfaces.

Verify connection and authorization before running tasks

Before executing any Parseur operation, users can verify that the parseur connection is ACTIVE and follow the returned authorization link if setup is incomplete.

Run automated steps within one session

When a workflow requires search, connection checks, and tool execution, users can reuse the same session ID to organize the full flow and handle pagination when needed.

// docs

AI summary

The README explains how to automate Parseur operations through Rube MCP using Composio's Parseur toolkit. It covers prerequisites, connection and authorization setup, the required search-first workflow, and key execution practices such as session reuse, strict schema compliance, always including the memory parameter, and handling pagination. It also provides a quick reference for discovering tools, checking connections, and running execution calls.

Show full docs ▾

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

// FAQ

What does this skill do?

It automates Parseur operations through Rube MCP using Composio's Parseur toolkit. The docs emphasize searching tools first, checking the connection, and then executing with the discovered schema.

What are the prerequisites?

Your client must have Rube MCP connected, and RUBE_SEARCH_TOOLS must be available. You also need an active connection for the parseur toolkit via RUBE_MANAGE_CONNECTIONS.

Why must I search tools first?

Because tool schemas may change, the docs explicitly say not to hardcode tool slugs or arguments. You should call RUBE_SEARCH_TOOLS first to get the current schema before proceeding.

Automate Mapulus tasks via Rube MCP using the latest tool schemas.

ComposioGet→

$ loading_