tisane-automation

Tisane Automation - Automating Tisane Tasks via Rube MCP

Skill Overview

Automate Tisane tasks through Composio’s Rube MCP server, enabling tool discovery, connection management, and batch execution without requiring an API key.

Use Cases

1. Integrating Tisane Workflows with Claude

When you need to integrate Tisane functionality into a Claude skill, this skill provides a complete MCP connection solution. Simply add the Rube MCP endpoint to the client configuration to access the Tisane toolkit through the standard MCP protocol, without writing additional API call code.

2. Automating Tisane Batch Operations

For Tisane tasks that need to be executed repeatedly, use RUBE_REMOTE_WORKBENCH together with the run_composio_tool() function for batch processing. The skill supports session reuse and pagination, ensuring the stability and completeness of large-scale data operations.

3. Dynamic Tool Discovery and Execution

Tisane tool schemas are updated frequently. This skill requires calling RUBE_SEARCH_TOOLS first to retrieve the latest schemas, ensuring that parameter formats are correct during execution. It is suitable for automation workflows that require long-term maintenance and helps prevent execution failures caused by changes to tool schemas.

Core Features

Tool Discovery and Schema Validation

Use RUBE_SEARCH_TOOLS to retrieve the currently available Tisane tools, input schemas, recommended execution plans, and known pitfalls in real time. The results include the correct tool_slug and parameter structures, avoiding execution errors caused by hardcoded, outdated information.

Connection Management and Status Checks

Use RUBE_MANAGE_CONNECTIONS to manage Tisane connection status, with support for detecting statuses such as ACTIVE, PENDING_AUTH, and EXPIRED. The skill verifies the connection status before execution to ensure that workflows run with a valid connection and avoid task failures caused by connection issues.

Multi-Tool Batch Execution

RUBE_MULTI_EXECUTE_TOOL supports executing multiple Tisane tools in a single call and provides a memory parameter for passing data between tools. Session IDs can be reused throughout the workflow, improving the efficiency of multi-step tasks.

Frequently Asked Questions

How do I add Rube MCP to the client configuration?

Add the following to the configuration file of Claude or another MCP client:

{
  "mcpServers": {
    "rube": {
      "url": "https://rube.app/mcp"
    }
  }
}

No API key configuration is required. Once the endpoint is added, you can use it immediately. Afterward, call RUBE_SEARCH_TOOLS to verify that the connection was successful.

What should I do if the Tisane connection is shown as inactive?

Authentication is required the first time you use it. After calling RUBE_MANAGE_CONNECTIONS, if the status is PENDING_AUTH, the response will include an authorization link. Visit the link to link your Tisane account, then call the connection management interface again to confirm that the status has changed to ACTIVE before using it normally.

Why must RUBE_SEARCH_TOOLS be called first every time?

The tool_slug and parameter schemas of the Composio toolkit are updated frequently, and hardcoding this information can easily cause execution failures. RUBE_SEARCH_TOOLS returns real-time schemas containing accurate parameter structures and known pitfalls, ensuring stable execution. The core principle of this skill is “Always search tools first,” which is the best practice for ensuring long-term maintainability.