Epic Games EOS MCP. Query account details and friend connections instantly.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Epic Games EOS MCP Server connects your AI client to Epic Online Services (EOS). Look up public account metadata, check friend lists, and search the full Epic Games Store catalog.
Use your AI agent to interact with the entire Epic Games ecosystem, verifying cross-platform identity and managing social connections directly from chat.
What your AI agents can do
Get account info
Retrieves public metadata and linked platforms for one or more Epic Account IDs.
Get friends list
Retrieves the current list of friends associated with a specific Epic account ID.
Search store catalog
Searches the Epic Games Store catalog using a valid Sandbox or Deployment ID.
Retrieves public metadata and display names for one or more Epic Account IDs.
Pulls the friend list for a specific Epic account ID.
Finds products and services by searching the Epic Games Store catalog.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Epic Games EOS MCP Server: 3 Tools for Account Data
Use these tools to retrieve public account details, pull friend lists, and search the full Epic Games Store catalog using your AI agent.
019d8435get account info
Retrieves public metadata and linked platforms for one or more Epic Account IDs.
019d8435get friends list
Retrieves the current list of friends associated with a specific Epic account ID.
019d8435search store catalog
Searches the Epic Games Store catalog using a valid Sandbox or Deployment ID.
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 every 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 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Epic Games EOS MCP Server lets your AI client talk to Epic Online Services (EOS). You can use this server to check account details, see who a user' friends are, and search the whole Epic Games Store. Your agent interacts with the whole Epic Games system, letting you verify cross-platform identities and manage social connections right from your chat.
get_account_info retrieves public metadata and linked platforms for one or more Epic Account IDs. get_friends_list pulls the current list of friends tied to a specific Epic account ID. search_store_catalog searches the Epic Games Store catalog using a valid Sandbox or Deployment ID.
How Epic Games EOS MCP Works
- 1 Subscribe to the server and get your Epic Client ID and Client Secret.
- 2 Input the credentials into your AI client.
- 3 Start querying account data or searching the store directly through your chat interface.
The bottom line is, you give your agent the credentials, and it handles the API calls to the Epic Games backend for you.
Who Is Epic Games EOS MCP For?
Game developers need to verify account info and social states fast. Community managers use this to look up player profiles and external links. Gaming enthusiasts want to interact with their Epic social graph using AI, eliminating manual API calls.
Verifies account metadata and social statuses during the development cycle.
Looks up player profiles and verifies external account links for user support.
Tests account state transitions and friend list functionality against defined criteria.
What Changes When You Connect
- Check account status and cross-platform links: Use
get_account_infoto pull public metadata and see which external platforms (Steam, Xbox, PSN) an Epic account is connected to. No more manually cross-referencing developer dashboards. - Manage social connections easily: The
get_friends_listtool lets your agent pull a user's entire friend list without you writing a single API call or managing pagination. - Discover products in the store:
search_store_cataloglets you query the entire Epic Games Store catalog using your AI client. You can find specific products or check availability based on defined sandboxes. - Accelerate development: Developers can use these tools to quickly verify account info and social states while testing game features, cutting down on manual testing cycles.
- Handle support queries faster: Community Managers use this to look up player profiles and external links instantly, giving support agents reliable data in chat.
- Stay in the ecosystem: Your agent can manage the entire social graph—from checking accounts to finding related products—keeping all data retrieval within the Epic ecosystem.
Real-World Use Cases
Debugging a Player's Account State
A QA engineer needs to know if a player's account is linked to both Steam and PlayStation. Instead of logging into multiple developer portals, they prompt their agent: 'What is the account info for Epic ID X?' The agent runs get_account_info, instantly confirming all linked platforms and metadata. Debugging is solved in a single chat turn.
Onboarding a New Community Member
A community manager gets a user ticket asking for a list of friends to check on a collaborative project. They ask the agent to run get_friends_list for the user. The agent retrieves the full list, which the manager then uses to follow up with the correct people, eliminating manual lookups.
Checking Product Availability for a Demo
A game developer needs to verify if a specific asset is available in a particular test sandbox. They run search_store_catalog with the required deployment ID. The agent returns a precise list of matching products, confirming if the demo environment is correctly provisioned for testing.
Building a User Profile Page
A developer building a client-side profile page needs to display the user's display name and associated platforms. They use get_account_info to fetch the required data points, feeding the clean JSON output directly into their application logic without writing boilerplate API wrappers.
The Tradeoffs
Using multiple separate APIs
Trying to get account data by hitting the Epic API, then calling a Steam API, and then making a separate GraphQL query for friends. This requires complex orchestration code and fails if any single service is down.
→
Use the Epic Games EOS MCP Server. Your agent handles the multi-step process. You just ask for 'The account info and friends list for ID X,' and the agent executes get_account_info and get_friends_list sequentially, giving you a unified result.
Assuming data is always fresh
Running a get_friends_list query, but the list is stale because the backend update process was delayed. You spend time debugging why the data is wrong.
→ Treat the data as live. The MCP Server calls the current EOS API endpoints, giving you the most up-to-date data available through the service. Always verify the retrieval date if data freshness is a requirement.
Hardcoding IDs in client code
Writing code that assumes a user's Steam ID or Epic ID will never change. When the user updates their profile, your hardcoded link breaks, and the application fails.
→
Always use the agent to fetch the current ID details via get_account_info. The agent provides the necessary, up-to-date public metadata, ensuring your application links remain accurate.
When It Fits, When It Doesn't
Use this if you need to build workflows around core identity data: linking accounts, checking social connections, or discovering store products. You need your AI client to act as a wrapper for multiple Epic APIs. Don't use this if you only need to read static data from a database—just query the DB directly. Also, don't use this if you need deep, private user actions (like purchasing or changing passwords); you'll need a specialized transaction API for that. This server is for reading public metadata, social graphs, and catalog data only.
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 INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 3 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Checking a user's profile used to mean jumping between three different developer portals.
Before the EOS MCP Server, checking a single user meant logging into the Epic Dev Portal for account IDs, then switching to the Steam API for external links, and finally hitting a separate database just for friend status. It was a copy-paste nightmare, and the data was rarely fully synchronized.
Now, you ask your agent to check the user. The agent runs `get_account_info` and `get_friends_list` through the MCP Server. You get a single, unified response containing the account metadata, linked platforms, and the current friend list—all in one chat reply.
Epic Games EOS MCP Server: Get Account Details
Manually verifying a user's platform links and public display name involved hitting multiple, undocumented endpoints. You had to stitch together data points from various sources to build a complete picture of the user's identity.
The MCP Server handles that complexity. You just use the `get_account_info` tool, and it returns a clean, structured object detailing the user's identity across the entire Epic ecosystem.
Common Questions About Epic Games EOS MCP
How do I use the get_account_info tool with the Epic Games EOS MCP Server? +
You prompt your agent with the desired Epic Account ID. The agent runs get_account_info and returns public details, including the display name and any linked platforms. It's a direct query.
Can I get a friend list using the get_friends_list tool? +
Yes, you give the agent the target Epic ID, and it executes get_friends_list. The result is a structured list of IDs that are currently marked as friends in the EOS system.
Does search_store_catalog require special keys? +
Yes. The search_store_catalog tool requires a valid Sandbox or Deployment ID to function. You must provide this ID to the agent for the search to work.
Is the data from the Epic Games EOS MCP Server real-time? +
The server connects directly to EOS. While it's not instantaneous, it pulls the most current public data available through the official Epic Games API endpoints.
What is the scope of the get_account_info tool for cross-platform data? +
The get_account_info tool verifies public metadata and display names for Epic Account IDs. It also verifies external authentication links, like Steam or PlayStation Network, associated with the account.
Can the get_friends_list tool handle large social graphs or multiple accounts? +
The get_friends_list tool retrieves the friend list for a single, specified Epic account. For multiple accounts, you must run the tool sequentially for each individual ID.
Are there any limitations or rate limits when using search_store_catalog? +
While the server supports searching the store catalog, usage is subject to the rate limits set by Epic Online Services. We recommend implementing exponential backoff in your agent logic.
What information is required to successfully use search_store_catalog? +
To use the search_store_catalog tool, you must provide valid Sandbox or Deployment IDs. These identifiers are necessary to scope the search within the correct Epic Games environment.
How do I get an Epic Client ID and Secret? +
You must create a developer account at dev.epicgames.com, set up an organization and a product, and generate credentials in the 'Product Settings' section.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Tencent Cloud VOD / 腾讯云点播
Tencent's dominant video-on-demand platform — manage media, track tasks, and audit storage via AI.
Huawei Push Kit / 华为推送服务
Huawei's essential device push platform — send notifications to HMS devices via AI.
Google Forms
Analyze datasets actively — list active Google Forms, query exact responses, and fetch metadata programmatically.
You might also like
Tana
Connect your AI to Tana. Build intelligent knowledge graphs, define supertags, and capture dynamic nested nodes directly from the prompt.
Kustomer
Manage customer service — list conversations, audit customers, and search timelines.
Gladia (Speech AI)
Transcribe, translate, and analyze audio with Gladia's high-speed Speech AI — support for pre-recorded files and live streaming.