How to integrate Epic games MCP with Claude Agent SDK

This guide walks you through connecting Epic games to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Epic games agent that can list your recently purchased epic games titles, show current fortnite store offers, check your unreal engine license details through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Epic games account through Composio's Epic games MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Epic games logoEpic games
Oauth2

Epic Games is a leading video game publisher and digital storefront, known for Fortnite and Unreal Engine. It lets gamers access, manage, and purchase games all in one place.

28 Tools

Introduction

This guide walks you through connecting Epic games to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Epic games agent that can list your recently purchased epic games titles, show current fortnite store offers, check your unreal engine license details through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Epic games account through Composio's Epic games MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Epic games with

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Epic games
  • Configure an AI agent that can use Epic games as a tool
  • Run a live chat session where you can ask the agent to perform Epic games operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

What is the Epic games MCP server, and what's possible with it?

The Epic games MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Epic games account. It provides structured and secure access to your Epic Games platform, so your agent can perform actions like accessing your game library, tracking new releases, viewing purchase history, and managing your account details on your behalf.

  • Game library insights: Let your agent retrieve and summarize information about your owned and recently played games.
  • Store browsing and recommendations: Have the agent help you discover new games, sales, and curated recommendations from the Epic Games Store.
  • Purchase history overview: Get quick reports on your past purchases, including receipts and downloadable content.
  • Account management assistance: Allow your agent to help update profile details, privacy settings, or linked accounts for a streamlined experience.
  • Stay up-to-date on releases: Ask the agent to notify you about upcoming game launches, updates, or major events within the Epic Games ecosystem.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Epic games account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Epic games functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Epic games
  const session = await composio.create(USER_ID, {
    toolkits: ['epic_games'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Epic games
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Epic games tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Epic games
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Epic games and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['epic_games']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Epic games tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Epic games through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS

Supported Tools

Every Epic games action and event your agent gets out of the box.

Delete Preset Metadata Key

Tool to delete a metadata key-value pair associated with a Remote Control Preset.

Get Island Metadata

Tool to fetch metadata for a specific Fortnite island by its code.

Get Island Average Minutes per Player

Tool to retrieve average minutes per unique player for a given island code and interval.

Get Island Favorites Metrics

Tool to fetch how many times an island was added to favorites over a time interval.

Get Island Metrics by Interval

Tool to retrieve usage metrics for a Fortnite island aggregated by interval.

Get Island Minutes Played

Tool to retrieve total minutes played on an island during a given interval.

Get Island Peak CCU

Tool to retrieve peak concurrent users for an island.

Get Island Plays

Tool to retrieve the number of plays (session starts) for a Fortnite island.

Get Island Recommendations

Tool to retrieve the count of player recommendations for an island.

Get Island Retention

Tool to retrieve day-over-day retention metrics for a Fortnite island.

Get Island Unique Players

Tool to retrieve the number of unique players who played an island over a specific interval.

Get Remote Control Preset

Tool to get details for a specific Remote Control Preset by name.

Get Preset Metadata

Tool to retrieve all metadata entries associated with a preset.

Get Preset Metadata Key

Tool to read a single metadata key's value for a Remote Control Preset.

Get Preset Property

Tool to read the value(s) of a property exposed through a Remote Control Preset.

List Blueprint-Callable Functions

Tool to list blueprint-callable functions on a UObject.

List Fortnite Islands

Tool to list public discoverable Fortnite islands sorted by newest releases first.

Remote API CORS Preflight

Tool to perform a CORS preflight OPTIONS request to the Remote Control API.

Call UObject Blueprint Function

Tool to invoke a Blueprint-callable function on an in-memory UObject.

Describe a UObject

Tool to describe a UObject.

Wait for UObject Event (Experimental)

Tool to block until the next specified UObject event occurs.

Put UObject Property

Tool to read or set a UObject's property values.

Get Object Thumbnail

Tool to fetch the Content Browser thumbnail image for a specified asset.

Invoke Preset Function

Tool to invoke a function in a Remote Control Preset.

Put Preset Metadata Key

Tool to create or update a metadata key on a Remote Control Preset.

Update Preset Property

Tool to update a property exposed through a Remote Control Preset.

Batch Remote Control Requests

Tool to batch multiple Remote Control API calls into a single request.

Initiate Remote Control Session

Tool to initiate a Remote Control session.

FAQ

Frequently asked questions

With a standalone Epic games MCP server, the agents and LLMs can only access a fixed set of Epic games tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Epic games and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Agent SDK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Epic games tools.

Yes, absolutely. You can configure which Epic games scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Epic games data and credentials are handled as safely as possible.

Start with Epic games.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Epic games tool your agent needs.Free to start.

Start building