Ayrshare Automation

What This Skill Does

This skill automates Ayrshare operations using Composio's Ayrshare toolkit through Rube MCP. It allows users to manage their social media posting and analytics programmatically. It is designed for social media managers and marketers who want to automate their Ayrshare workflows.

When to Use

Schedule social media posts. Automate content distribution across platforms. Track social media engagement metrics. Manage multiple social media accounts. Generate social media reports. Automate social listening tasks.

Key Features

Uses Rube MCP for tool discovery and execution. Requires an active Ayrshare connection via RUBE_MANAGE_CONNECTIONS. Employs RUBE_SEARCH_TOOLS to get current tool schemas. Follows a discover, connect, execute workflow pattern. Provides error handling and connection status checks. Ensures schema compliance for tool arguments.

Manual Installation

Ayrshare Automation via Rube MCP

Automate Ayrshare operations through Composio's Ayrshare toolkit via Rube MCP. Toolkit docs: composio.dev/toolkits/ayrshare

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Ayrshare connection via RUBE_MANAGE_CONNECTIONS with toolkit ayrshare 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 ayrshare 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: "Ayrshare 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

queries: [{use_case: "your specific Ayrshare task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["ayrshare"] 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: {}

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

Powered by Composio