Abyssale Automation via Rube MCP

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

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

Toolkit docs: composio.dev/toolkits/abyssale

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Abyssale connection via RUBE_MANAGE_CONNECTIONS with toolkit abyssale
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

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.

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Abyssale operations", known_fields: ""}]
session: {generate_id: true}

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Abyssale-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `abyssale`
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`

abyssale-automation