Rube MCP is the management protocol that connects to Composio’s MCP server at rube.app, enabling search, management, and execution of toolkit tools.

Do I need an active Documint connection?

Yes, ensure RUBE_MANAGE_CONNECTIONS for toolkit 'documint' returns ACTIVE before executing tools.

Why always call RUBE_SEARCH_TOOLS?

Tool schemas change; this ensures you use current tool slugs and required arguments, preventing failures.

documint-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Documint Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/documint

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["documint"]
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 Documint-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `documint`
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/documint-automation/SKILL.mdView on GitHub

Overview

Automate Documint operations through Composio's Documint toolkit via Rube MCP. The skill orchestrates tool discovery, connection management, and execution to streamline repetitive Documint workflows.

How This Skill Works

First, use RUBE_SEARCH_TOOLS to discover current Documint tool slugs and schemas. Then verify the connection with RUBE_MANAGE_CONNECTIONS and ensure status is ACTIVE. Finally execute a tool with RUBE_MULTI_EXECUTE_TOOL, passing the discovered tool_slug, schema-compliant arguments, memory, and the session_id.

When to Use It

Automating routine Documint tasks that update often due to schema changes.
When you must rely on up-to-date tool schemas before running workflows.
Integrating Documint steps into a broader Composio automation flow.
Ensuring ACTIVE connections and session reuse within a workflow.
Running bulk Documint operations through remote bench tools.

Quick Start

Step 1: Discover tools with RUBE_SEARCH_TOOLS (Documint use_case).
Step 2: Establish/verify connection with RUBE_MANAGE_CONNECTIONS and ensure ACTIVE.
Step 3: Execute a tool with RUBE_MULTI_EXECUTE_TOOL using memory and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing.
Use exact field names/types from the search results.
Always include memory (even empty) in RUBE_MULTI_EXECUTE_TOOL calls.
Reuse session IDs when appropriate; avoid creating new sessions for existing workflows.

Example Use Cases

Automate monthly Documint document generation with dynamic tool schemas.
Batch-process thousands of Documint tasks by discovering tools first.
Integrate Documint actions into a larger Composio automation pipeline.
Validate tool arguments against current schemas before running.
Use remote bench to run multiple tools in parallel for a project.

Frequently Asked Questions

Add this skill to your agents