Fibery Automation

What This Skill Does

This skill automates Fibery operations using Composio's Fibery toolkit through Rube MCP. It is designed for users who want to automate tasks within Fibery, such as creating, updating, and managing entities. The skill handles connection management, tool discovery, and execution.

When to Use

• Automate Fibery entity creation.
• Update Fibery entities automatically.
• Manage Fibery relations.
• Extract data from Fibery.
• Sync Fibery with other tools.
• Automate Fibery reports.

Key Features

• Connects to Fibery via Rube MCP.
• Discovers available Fibery tools dynamically.
• Enforces schema compliance for tool arguments.
• Manages Fibery connection status.
• Provides a structured workflow pattern.
• Offers guidance on avoiding common errors.

Manual Installation

Fibery Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/fibery

Prerequisites

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

Step 2: Check Connection

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