How to integrate Epic games MCP with OpenAI Agents SDK

This guide walks you through connecting Epic games to the OpenAI Agents 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 OpenAI Agents 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 OpenAI Agents 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 OpenAI Agents 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 OpenAI 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 OpenAI Agents SDK?

The OpenAI Agents SDK is a lightweight framework for building AI agents that can use tools and maintain conversation state. It provides a simple interface for creating agents with hosted MCP tool support.

Key features include:

  • Hosted MCP Tools: Connect to external services through hosted MCP endpoints
  • SQLite Sessions: Persist conversation history across interactions
  • Simple API: Clean interface with Agent, Runner, and tool configuration
  • Streaming Support: Real-time response streaming for interactive applications

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 OpenAI API Key
  • Primary know-how of OpenAI Agents SDK
  • A live Epic games project
  • Some knowledge of Python or Typescript
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
3

Install dependencies

npm install @composio/openai-agents @openai/agents dotenv

Install the Composio SDK and the OpenAI Agents SDK.

4

Set up environment variables

bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com

Create a .env file and add your OpenAI and Composio API keys.

5

Import dependencies

import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';
What's happening:
  • You're importing all necessary libraries.
  • The Composio and OpenAIAgentsProvider classes are imported to connect your OpenAI agent to Composio tools like Epic games.
6

Set up the Composio instance

dotenv.config();

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});
What's happening:
  • dotenv.config() loads your .env file so COMPOSIO_API_KEY and USER_ID are available as environment variables.
  • Creating a Composio instance using the API Key and OpenAIAgentsProvider class.
7

Create a Tool Router session

// Create Tool Router session for Epic games
const session = await composio.create(userId as string, {
  toolkits: ['epic_games'],
});
const mcpUrl = session.mcp.url;

What is happening:

  • You give the Tool Router the user id and the toolkits you want available. Here, it is only epic_games.
  • The router checks the user's Epic games connection and prepares the MCP endpoint.
  • The returned session.mcp.url is the MCP URL that your agent will use to access Epic games.
  • This approach keeps things lightweight and lets the agent request Epic games tools only when needed during the conversation.
8

Configure the agent

// Configure agent with MCP tool
const agent = new Agent({
  name: 'Assistant',
  model: 'gpt-5',
  instructions:
    'You are a helpful assistant that can access Epic games. Help users perform Epic games operations through natural language.',
  tools: [
    hostedMcpTool({
      serverLabel: 'tool_router',
      serverUrl: mcpUrl,
      headers: { 'x-api-key': composioApiKey },
      requireApproval: 'never',
    }),
  ],
});
What's happening:
  • We're creating an Agent instance with a name, model (gpt-5), and clear instructions about its purpose.
  • The agent's instructions tell it that it can access Epic games and help with queries, inserts, updates, authentication, and fetching database information.
  • The tools array includes a hostedMcpTool that connects to the MCP server URL we created earlier.
  • The headers object includes the Composio API key for secure authentication with the MCP server.
  • requireApproval: 'never' means the agent can execute Epic games operations without asking for permission each time, making interactions smoother.
9

Start chat loop and handle conversation

// Keep conversation state across turns
const conversationSession = new OpenAIConversationsSession();

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

console.log('\nComposio Tool Router session created.');
console.log('\nChat started. Type your requests below.');
console.log("Commands: 'exit', 'quit', or 'q' to end\n");

try {
  const first = await run(agent, 'What can you help me with?', { session: conversationSession });
  console.log(`Assistant: ${first.finalOutput}\n`);
} catch (e) {
  console.error('Error:', e instanceof Error ? e.message : e, '\n');
}

rl.prompt();

rl.on('line', async (userInput) => {
  const text = userInput.trim();

  if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
    console.log('Goodbye!');
    rl.close();
    process.exit(0);
  }

  if (!text) {
    rl.prompt();
    return;
  }

  try {
    const result = await run(agent, text, { session: conversationSession });
    console.log(`\nAssistant: ${result.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();
});

rl.on('close', () => {
  console.log('\n👋 Session ended.');
  process.exit(0);
});
What's happening:
  • The program prints a session URL that you visit to authorize Epic games.
  • After authorization, the chat begins.
  • Each message you type is processed by the agent using run().
  • The responses are printed to the console.
  • Typing exit, quit, or q cleanly ends the chat.

Complete Code

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

import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});

async function main() {
  // Create Tool Router session
  const session = await composio.create(userId as string, {
    toolkits: ['epic_games'],
  });
  const mcpUrl = session.mcp.url;

  // Configure agent with MCP tool
  const agent = new Agent({
    name: 'Assistant',
    model: 'gpt-5',
    instructions:
      'You are a helpful assistant that can access Epic games. Help users perform Epic games operations through natural language.',
    tools: [
      hostedMcpTool({
        serverLabel: 'tool_router',
        serverUrl: mcpUrl,
        headers: { 'x-api-key': composioApiKey },
        requireApproval: 'never',
      }),
    ],
  });

  // Keep conversation state across turns
  const conversationSession = new OpenAIConversationsSession();

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

  console.log('\nComposio Tool Router session created.');
  console.log('\nChat started. Type your requests below.');
  console.log("Commands: 'exit', 'quit', or 'q' to end\n");

  try {
    const first = await run(agent, 'What can you help me with?', { session: conversationSession });
    console.log(`Assistant: ${first.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();

  rl.on('line', async (userInput) => {
    const text = userInput.trim();

    if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
      console.log('Goodbye!');
      rl.close();
      process.exit(0);
    }

    if (!text) {
      rl.prompt();
      return;
    }

    try {
      const result = await run(agent, text, { session: conversationSession });
      console.log(`\nAssistant: ${result.finalOutput}\n`);
    } catch (e) {
      console.error('Error:', e instanceof Error ? e.message : e, '\n');
    }

    rl.prompt();
  });

  rl.on('close', () => {
    console.log('\nSession ended.');
    process.exit(0);
  });
}

main().catch((err) => {
  console.error('Fatal error:', err);
  process.exit(1);
});

Conclusion

This was a starter code for integrating Epic games MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Epic games.

Key features:

  • Hosted MCP tool integration through Composio's Tool Router
  • SQLite session persistence for conversation history
  • Simple async chat loop for interactive testing
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. OpenAI Agents 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