Epic Games Automation

What This Skill Does

• This skill automates operations within Epic Games using Composio's Epic Games toolkit via Rube MCP.
• It's designed for users who need to streamline tasks within the Epic Games ecosystem. The skill ensures proper setup and connection before executing any workflows.

When to Use

Discover available Epic Games toolsCheck the status of the Epic Games connectionExecute specific Epic Games toolsAutomate game deployment processesManage user accounts in Epic GamesRetrieve game analytics data

Key Features

Automates Epic Games operations via Rube MCPUses Composio's Epic Games toolkitRequires an active Epic Games connectionDiscovers available tools before executionChecks connection status before running workflowsProvides a core workflow pattern for execution

Manual Installation

Manual installationView Full Skill ContentThe complete markdown content that gets installedEpic Games Automation via Rube MCP

Automate Epic Games operations through Composio's Epic Games toolkit via Rube MCP.

• Toolkit docs: composio.
• dev/toolkits/epic_games.

Prerequisites

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

Step 2: Check Connection

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