Rube MCP is Composio's multi-tool platform that lets you discover, connect, and execute Documenso tools via standardized commands.

No API keys are required — add the MCP endpoint (for example, https://rube.app/mcp) and authorize as needed.

What if tool schemas change?

Always search for tools before running. Tool slugs and argument structures can change, so update your workflow to reflect the latest schemas.

documenso-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Documenso Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/documenso

Prerequisites

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

Step 2: Check Connection

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

Overview

Documenso automation through Composio's toolkit using Rube MCP lets you run Documenso operations programmatically. It emphasizes discovering current tool schemas first with RUBE_SEARCH_TOOLS and validating an ACTIVE Documenso connection before execution. This approach keeps workflows aligned with live tool definitions.

How This Skill Works

You connect to Rube MCP at the specified endpoint, call RUBE_SEARCH_TOOLS to fetch available tools for your Documenso use case, then select a tool_slug from the results and execute it via RUBE_MULTI_EXECUTE_TOOL with the required arguments and a memory object. Before execution, verify the connection status with RUBE_MANAGE_CONNECTIONS and reuse a session_id across related calls.

When to Use It

Automate a specific Documenso operation after a tool schema update
Integrate a new Documenso workflow and need current tool schemas
Validate an ACTIVE Documenso connection before executing tools
Run multiple tools in a single session using RUBE_MULTI_EXECUTE_TOOL
Handle large tool catalogs by paginating tool results to fetch all options

Quick Start

Step 1: RUBE_SEARCH_TOOLS with a Documenso use_case to fetch tool schemas
Step 2: RUBE_MANAGE_CONNECTIONS to ensure the documenso toolkit is ACTIVE
Step 3: RUBE_MULTI_EXECUTE_TOOL with a discovered tool_slug, required arguments, memory, and the session_id

Best Practices

Always run RUBE_SEARCH_TOOLS before executing tools to get current tool slugs and schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution
Use exact field names and types from the tool schemas; avoid hardcoding slugs
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs across related steps and handle pagination when listing tools

Example Use Cases

Discover a Documenso task tool via RUBE_SEARCH_TOOLS and execute it to export a report
Connect to Documenso with Rube MCP and run a batch workflow using RUBE_MULTI_EXECUTE_TOOL
Update an automation after a tool schema change by re-running RUBE_SEARCH_TOOLS and adapting arguments
Build a multi-step workflow that reuses the same session_id across consecutive tool invocations
Fetch all tools from a large catalog by handling pagination tokens until complete

Frequently Asked Questions

Add this skill to your agents