Appveyor Automation

What This Skill Does

The Appveyor Automation skill enables users to automate operations within Appveyor through Composio's Appveyor toolkit, leveraging Rube MCP. It simplifies tasks related to continuous integration and deployment. This skill is useful for developers and Dev Ops engineers seeking to automate Appveyor workflows.

When to Use

Discover available Appveyor tools. Check the status of the Appveyor connection. Execute specific Appveyor tools. Automate build and deployment processes. Manage environment variables programmatically. Retrieve and process Appveyor build data.

Key Features

Automates Appveyor tasks via Rube MCP.Uses Composio's Appveyor toolkit. Requires an active Appveyor connection. Discovers tools dynamically using RUBE_SEARCH_TOOLS.Manages connections with RUBE_MANAGE_CONNECTIONS.Executes tools with RUBE_MULTI_EXECUTE_TOOL.

Appveyor Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/appveyor

Prerequisites

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

Step 2: Check Connection

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