# Epic Games EOS MCP

> Epic Games EOS MCP connects your AI client directly to the Epic Online Services backend. Use it to check public account details, pull friend lists, and search products across the entire Epic Games Store catalog. It’s how you turn natural language queries into actionable game data.

## Overview
- **Category:** industry-titans
- **Price:** Free
- **Tags:** player-metadata, social-graph, account-lookup, game-services, user-profiles

## Description

This connector lets your agent talk to Epic's core gaming infrastructure. Instead of logging into multiple developer portals or running complex scripts, you ask your AI client a question—like 'What devices is this account linked to?'—and get the answer instantly. You can pull public metadata for accounts, check who a player’s friends are, and search deep within the store's catalog using simple conversational prompts. It eliminates hours of API setup and data stitching. With Vinkius managing the connection, you connect once and gain access to this massive dataset through any compatible AI client. It’s essential for anyone who needs reliable, structured player identity and game metadata without writing a single line of boilerplate code.

## Tools

### get_account_info
Retrieves public profile information for one or more Epic Account IDs.

### get_friends_list
Pulls the current list of friends associated with a specific Epic account ID.

### search_store_catalog
Searches the live Epic Games Store catalog using required Sandbox or Deployment IDs.

## Prompt Examples

**Prompt:** 
```
Get account info for Epic ID '0123456789abcdef'.
```

**Response:** 
```
Retrieving data for ID '0123456789abcdef'... Display name: 'EpicExplorer'. This account is linked to Steam and PlayStation Network.
```

## Capabilities

### Determine Account Status
Retrieve public details, display names, and linked platforms for specific Epic Account IDs.

### Manage Social Connections
Fetch a player’s current friends list based on their unique account ID.

### Browse Game Products
Search the live Epic Games Store catalog using specific deployment or sandbox IDs.

## Use Cases

### Auditing a Player’s Profile
A community manager needs to know everything about a high-value player. They ask their agent, and it first runs `get_account_info` to grab the display name and linked platforms. Then, it uses `get_friends_list` to identify key contacts in that social graph.

### Validating a New Game Feature
A developer needs to confirm if a specific product exists in the store for testing. They prompt their agent with the necessary IDs, and it executes `search_store_catalog`, returning confirmation on availability before any actual deployment.

### Generating Onboarding Reports
A product analyst wants a report showing account data trends. They use the MCP to systematically run `get_account_info` for several test IDs, building a structured dataset that would otherwise require dozens of manual API calls.

### Checking Account Linkage
A QA engineer must confirm if an account ID is linked to multiple external services. They prompt the MCP, which utilizes its identity verification capabilities to report on Steam and PlayStation links simultaneously.

## Benefits

- Stop writing boilerplate API code. Instead of crafting multi-step scripts just to check a user's account status, you simply ask your agent, and it uses the `get_account_info` tool to return clean JSON data immediately.
- Quickly validate player identity. You can use the MCP to pull public metadata for any Epic Account ID, making onboarding and verification much faster than manual database checks.
- Understand social dynamics instantly. Needing a full friend list? The `get_friends_list` tool gives you this data point without ever leaving your chat window or IDE.
- Research the market effortlessly. Use the MCP to search the store catalog, pulling product details via `search_store_catalog` for competitive analysis—all from a single prompt.
- Work across platforms and services. The ability to check cross-platform identity links means you can confirm if an account is linked to Steam or PlayStation directly through your agent's query.

## How It Works

The bottom line is you talk to your AI client, and it handles all the complex API calls necessary to get accurate game data back to you.

1. Subscribe to this MCP and provide your required credentials: the Epic Client ID and Client Secret from the developer portal.
2. Your AI client authenticates with Vinkius, granting it access to the live EOS tools.
3. You ask your agent a question in plain language; it maps that request to the appropriate tool (e.g., fetching friend lists) and returns structured data.

## Frequently Asked Questions

**What does the Epic Games EOS MCP help with?**
This MCP connects your AI agent to Epic Online Services. It lets you look up public account metadata, retrieve friend lists, and search product details in the store catalog.

**Do I need developer credentials for get_account_info?**
Yes, you must subscribe with your valid Epic Client ID and Client Secret from the dev portal. This grants the MCP permission to query account data.

**Can I use this MCP just for friend lists?**
Absolutely. You can isolate the functionality by only querying the `get_friends_list` tool, which retrieves a player's current social network connections.

**Does search_store_catalog work for all products?**
No, `search_store_catalog` requires you to provide valid Sandbox or Deployment IDs. You must know where in the ecosystem you want to search.

**Is this MCP designed only for developers?**
Not necessarily. While useful for development, community managers and product analysts find it equally valuable for reporting and research purposes.