Epic Games
Epic Games is a video game developer and publisher known for titles like Fortnite and the Unreal Engine, offering an online store and platform
Verdict
Common use cases
- Check live player counts during launch
- Pull crash reports from latest build
- Review store rating trends weekly
- Monitor revenue by region in real time
- Summarize QA feedback before sprint planning
Integration
- Vendor
- Epic Games
- Category
- other
- Auth
- OAUTH2
- Composio slug
epic_games
Tools
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the MCP Integrations tab. 2. Click 'Add Integration' and select Epic Games from the directory. 3. You'll be redirected to Epic's OAuth consent screen — sign in with the Epic account that has developer or admin access to your organization. 4. Grant the requested scopes: these typically include read access to project metadata, analytics data, and store listings. 5. After authorizing, you'll return to Switchy and see 'Epic Games connected' with a green status indicator. 6. Open any Space and type '@Epic Games what's the current build status for [project name]?' to test the connection. 7. If the MCP responds with project data, you're ready to use it in workflows.
What teammates see: by default, memories from Epic Games are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Launch Day Health Check
@Epic Games show me the current concurrent player count, crash rate in the last 24 hours, and the top three user-reported issues for our latest release.Open in a Space →
Weekly Revenue Summary
@Epic Games summarize total revenue and in-app purchase breakdown by region for the last seven days.Open in a Space →
Build Status Before Deploy
@Epic Games what's the status of the most recent build for [project name]? Include any warnings or failed checks.Open in a Space →
Store Rating Trends
@Epic Games pull the average store rating and sentiment breakdown for reviews submitted in the last 30 days.Open in a Space →
Player Feedback Digest
@Epic Games analyze the last 100 player feedback submissions and list the top five recurring themes or feature requests.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Epic Games show me my library of owned games and which ones I haven't launched in the last 6 months
You own 47 games in your Epic Games library. 12 games haven't been launched in the last 6 months: Control, Hitman 3, Metro Exodus, Remnant: From the Ashes, Borderlands 3, Satisfactory, Kena: Bridge of Spirits, Chivalry 2, Prey, Death Stranding, Alan Wake Remastered, and A Plague Tale: Innocence. The most recent purchase was Alan Wake 2 (launched 3 times in the past month). This data reflects your account activity through yesterday.
This example assumes the MCP can read library ownership and launch history via Epic's platform APIs. OAuth2 scope must include read access to account entitlements and playtime data. Epic's API rate limits are not publicly documented, so frequent polling may hit undisclosed thresholds.
@Epic Games add Hades to my wishlist and notify me when it goes on sale for under $15
Added Hades to your Epic Games wishlist. I've set a price alert for $15 USD or lower. You'll receive a notification here in this Space when the threshold is met. Current price: $24.99. Note that Epic's sale events (like Mega Sales) typically happen quarterly, and wishlist price tracking depends on the MCP's polling frequency—expect alerts within 24 hours of a price drop, not real-time.
This demonstrates a write action (wishlist modification) plus a conditional watch. The MCP must support both wishlist mutations and either webhook subscriptions or periodic price checks. Users should confirm whether price alerts are push-based or require the Space to remain active for polling.
@Epic Games compare my Fortnite playtime this season to last season and summarize whether I'm playing more solo or in squads
This season (Chapter 5, Season 1): 34 hours played—18 hours in squads, 12 hours solo, 4 hours in creative mode. Last season: 41 hours—23 hours squads, 15 hours solo, 3 hours creative. You're playing 17% less overall this season, with the drop concentrated in squad matches. Solo playtime decreased by 20%, but your solo win rate improved from 8% to 12%. The shift suggests you're playing fewer but higher-quality solo sessions.
This synthesis example pairs Epic's playtime API with the AI's ability to calculate trends and infer patterns. Requires OAuth2 scope for detailed match history. Fortnite stats are game-specific—other Epic titles may expose less granular telemetry. The MCP's data freshness depends on Epic's API update cadence, typically within a few hours of match completion.
Use-case deep-dives
When Epic's MCP fits a Unreal Engine CI workflow
A 6-person indie studio shipping an Unreal project wants their build server to pull asset metadata and version info without manual logins. The Epic Games MCP uses OAuth2, so your CI runner can authenticate once and query project state across builds. This works if your team already lives in Epic's ecosystem—Unreal projects, Epic Online Services, maybe the asset store. The trade-off: if you're only using Epic for distribution (not development), the MCP adds OAuth overhead for minimal return. It's the right call when your build or release process needs programmatic access to Epic project data, and your team is comfortable managing OAuth tokens in a shared workspace. If you're just launching a game and checking download stats manually, skip it.
Pulling Epic Online Services metrics into team chat
A 10-person live-ops team runs a multiplayer game on Epic Online Services and needs daily active user counts, matchmaking queue lengths, and store revenue in their Slack standup. The Epic Games MCP can surface that telemetry if Epic exposes the right endpoints—but with zero tools captured yet, you're betting on future scope. OAuth2 means the integration persists across sessions, which matters for a dashboard that runs every morning. The boundary: if Epic's API doesn't cover the metrics you need, you'll still be logging into the dev portal manually. This is a strong fit if your team already queries Epic's backend for ops data and wants to centralize it in Switchy. If you're still figuring out what metrics matter, wait until the tool list fills in.
When Epic's MCP helps QA triage cross-platform issues
A 4-person QA team testing a cross-platform Unreal game needs to correlate crash reports from Epic's backend with internal bug tickets. The Epic Games MCP could pull crash logs or player session data if those tools exist, letting QA paste context into Linear or Jira without switching tabs. OAuth2 means the connection stays live across QA cycles. The catch: with no tools listed yet, you're assuming Epic built the MCP for this use-case. If the MCP only covers store or account management, it won't help QA. This is worth trying if your QA process already involves Epic's developer portal and you want to reduce context-switching. If your bugs come from in-game telemetry or third-party crash tools, this MCP won't close the loop.
Frequently asked
What does the Epic Games MCP do in Switchy?
It connects your Epic Games account to Switchy's AI workspace so your team can query game data, player stats, or store information without leaving the chat. Since Epic hasn't published specific tools yet, the integration currently handles OAuth authentication and will expose read/write capabilities as Epic documents them. You'll see available actions appear in the MCP directory once Epic releases the toolset.
Do I need an Epic Games developer account to connect this MCP?
You need an Epic account with OAuth credentials, which typically means registering as a developer in the Epic Games Developer Portal. Standard player accounts won't work because OAuth2 requires a client ID and secret. If you're connecting for a team, make sure the account has access to the games or services you want to query through Switchy.
Can this MCP purchase games or manage my Epic wallet?
No. MCPs in Switchy are read-focused by design, and Epic's OAuth scopes don't grant payment or wallet mutation access through third-party integrations. If you need to buy games or manage transactions, do that directly in the Epic launcher or website. This integration is for pulling data into your team's AI workflows, not executing purchases.
Why use this instead of just checking the Epic Games launcher?
The launcher is fine for one person playing games, but terrible for a team that needs to pull player stats, match history, or store metadata into a shared AI workspace. The MCP lets you ask questions like "show our clan's win rate this month" and get answers in Switchy's chat without alt-tabbing or copying data manually.
Who on my team should connect the Epic Games MCP?
Whoever owns the Epic developer credentials your team uses. If you're a game studio, that's probably your backend engineer or DevOps lead. If you're a community manager tracking player engagement, connect your own account. Only one person needs to authenticate; the whole Switchy workspace can then query the connected Epic data.