Epic Games EOS MCP. Check player data, friends lists, and store catalogs.
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.
Give Claude and any AI agent real-world access
Retrieve public details, display names, and linked platforms for specific Epic Account IDs.
Fetch a player’s current friends list based on their unique account ID.
Search the live Epic Games Store catalog using specific deployment or sandbox IDs.
Ask an AI about this
Waiting for input…
What AI agents can do with Epic Games EOS: 3 Tools Available
These three tools allow your agent to manage everything from querying individual user accounts to searching the entire product catalog.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Epic Games EOS MCPGet 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.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Epic Games EOS, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Epic Games EOS. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Dealing with fragmented gaming data points is exhausting.
Right now, getting a full picture of a player's standing requires jumping through hoops. You check the account ID in one dashboard, then you open another tool to find their friends list. If you need store details, you switch contexts entirely and start manually looking up product IDs.
With this MCP, all that data comes together. Your agent handles the cross-referencing. Instead of juggling multiple tabs and copy-pasting credentials, you ask a single question, and it pulls account metadata, friend links, and store details into one coherent answer.
Accessing Player Identity Data
The manual steps—verifying the account link status, pulling the friends list manually, and cross-referencing public metadata—are gone. The MCP handles all of that complex logic behind the scenes.
Now you just talk to your agent. It knows exactly which tool to run to give you the clean data you need, making deep player analysis instantaneous.
What Epic Games EOS MCP does for your AI
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.
019d8435-478b-7085-9a66-9b25b6468ab4 How to set up Epic Games EOS MCP
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.
Subscribe to this MCP and provide your required credentials: the Epic Client ID and Client Secret from the developer portal.
Your AI client authenticates with Vinkius, granting it access to the live EOS tools.
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.
Who uses Epic Games EOS MCP
Game developers who are tired of writing repetitive boilerplate code for player validation. Community managers struggling with manual profile lookups. Product analysts needing rapid access to large-scale social and product metadata.
Using the MCP, you quickly verify account data or check friend connections during a test build without setting up complex local testing environments.
You look up player profiles and external links for specific users to manage community outreach efficiently.
You pull large datasets of account metadata or store catalog details to spot trends that manual analysis would miss.
Benefits of connecting Epic Games EOS MCP
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.
Epic Games EOS MCP 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.
Epic Games EOS MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Hardcoding API calls
Writing a 100-line Python script that requires manually handling OAuth tokens, passing multiple parameters for account IDs, and parsing JSON responses before doing anything useful.
Just ask your agent. Use the MCP to initiate data retrieval with a simple prompt like 'Get account info for ID X.' Your AI client handles all the token management and structure through the get_account_info tool.
Ignoring Scope Limitations
Trying to use generic database queries when you actually need specific, structured game data like friend lists or store catalog items.
Don't query the general database. Use the specialized tools in this MCP. For social connections, always start with get_friends_list.
Bypassing Credentials
Running tests without providing valid Epic Client IDs and Secrets because you're trying to keep your setup simple.
You must provide the required credentials (Client ID/Secret) when subscribing. The system needs them for the MCP to execute any of its tools successfully.
When to use Epic Games EOS MCP
Use this MCP if your core problem revolves around structured player identity, social graphs, or product metadata within the Epic Games ecosystem. You need reliable access to public account details via get_account_info or friend lists via get_friends_list. Don't use it if you simply need general knowledge about gaming history; for that, a pure search engine tool is better. Also, don't use it if your goal is to modify the data (e.g., changing a username); this MCP only allows reading and querying information. If you are looking for broad competitor analysis across multiple unrelated services, you might need a more general multi-source connector.
Frequently asked questions about Epic Games EOS MCP
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.