Boldsign Automation via Rube MCP

SkillSearch

This skill connects your AI to BoldSign so it can send and manage e-signature documents for you. Once added, your AI can handle signing tasks, so documents go out and stay on track without you doing each step manually.

Available today. Use it from your connected AI after setup.

After adding it, ask your AI to search the available BoldSign actions first so it works with the current options, then hand it a document to send or manage.

Then ask your AI: use the Boldsign Automation via Rube MCP skill

What your AI can do with it

  • Send documents for e-signature through BoldSign
  • Manage e-signature documents as part of a task
  • Automate routine BoldSign signing tasks
  • Search available BoldSign actions first to find the right one before running a task

What this skill tells your AI

The instructions your AI receives, as published by composiohq/awesome-claude-skills in composio-skills/boldsign-automation/SKILL.md and read by ahel’s review.

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

Toolkit docs: composio.dev/toolkits/boldsign

Prerequisites

  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Boldsign connection via RUBE_MANAGE_CONNECTIONS with toolkit boldsign
  • 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.

  1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  2. Call RUBE_MANAGE_CONNECTIONS with toolkit boldsign
  3. If connection is not ACTIVE, follow the returned auth link to complete setup
  4. Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Boldsign 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 Boldsign task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["boldsign"]
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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Boldsign-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit boldsign
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef

Powered by Composio

Signals

GitHub stars
75k
Forks
9k
Last commit
Aug 2026
Advanced
Catalog kind
skill
Gateway key
boldsign-automation
Source
github.com/composiohq/awesome-claude-skills