What is Rube MCP and why do I need it for Signwell automation?

Rube MCP is a centralized control plane used to discover tool schemas, manage connections, and execute Signwell tools through a standard set of commands. It ensures you always have up to date tool definitions and active connections before running workflows.

How do I know my Signwell connection is ACTIVE?

Use RUBE_MANAGE_CONNECTIONS with the signwell toolkit and check the status field to confirm ACTIVE before executing any tools.

Can I bulk execute or reuse sessions for Signwell tasks?

Yes. You can batch using RUBE_MULTI_EXECUTE_TOOL and reuse session IDs for related workflows. Remember to provide memory even if it is empty and rely on current tool schemas discovered via RUBE_SEARCH_TOOLS.

signwell-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Signwell Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/signwell

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Signwell operations through Composio's Signwell toolkit via Rube MCP. It emphasizes discovering current tool schemas before each workflow and establishing an active connection prior to execution. This approach prevents hardcoded tool slugs and ensures schemas stay up to date.

How This Skill Works

Start with RUBE_SEARCH_TOOLS to fetch available Signwell tool schemas. Then verify or establish a connection with RUBE_MANAGE_CONNECTIONS for the signwell toolkit and ensure it is ACTIVE. Finally execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug, proper arguments, memory, and the session_id.

When to Use It

Automating a Signwell signing workflow end to end
Performing batch signings across multiple documents or recipients
Updating tool schemas or migrating workflows when RUBE_SEARCH_TOOLS returns new slugs
Reconnecting or validating a Signwell connection before critical operations
Reusing a session for related Signwell tasks to improve efficiency

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client config and verify RUBE_SEARCH_TOOLS responds
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit signwell and ensure the connection status is ACTIVE
Step 3: Discover tools with RUBE_SEARCH_TOOLS, pick a tool_slug, and execute via RUBE_MULTI_EXECUTE_TOOL with memory and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before attempting any workflow
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from search results, avoid hardcoding
Include memory parameter in RUBE_MULTI_EXECUTE_TOOL calls even when empty
Reuse session IDs for related workflows and handle pagination tokens when fetching tools

Example Use Cases

Discover a Signwell tool, then execute a signing workflow with a specific tool slug
Batch sign a list of documents for multiple recipients using a single session
Validate the current tool schemas after an update to avoid broken workflows
Reconnect signwell toolkit and perform a quick test run
Retrieve and verify document signing status after execution

Frequently Asked Questions

Add this skill to your agents