Epic Games MCP server for AI agents

Live

OAUTH 2.0

GAMING

Media

Epic Games gives your agent read access to a player's Epic Games account for gaming support and commerce: fetch the profile, list friends and blocked accounts, list entitlements and sandbox offers, and check whether the player owns a store item.

  • Per-user credentials: each call uses the actual user's token, never a shared bot.
  • Encrypted per-tenant vault: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: pre-call scope check, 90-day SIEM-exportable audit chain.
Epic Games
agent · Acme Q3
Run
Does this player own the Deluxe Edition?
S
epicgames_ecom_ownership_check
94ms
Player support agent
Yes. The connected player owns the Deluxe Edition item in your game's catalog.
Sources: 1 catalog item
epicgames
1 check
18:29
Message Claude...

Tools your gaming agent reaches for on Epic Games, scoped per user.

CALL ANY TOOL
7 read-only tools for gaming in Epic Games: read the player profile, list friends and blocked accounts, list entitlements and offers, and check item ownership.
epicgames_blocklist_list
List blocklist
List the accounts a player has blocked. Returns entries with accountId and created. Use epicgames_friends_get when the friends list is also needed. Requires the basic_profile and friends_list scopes.
Parameters
Name
Type
Required
Description
account_id
string
Required
Epic Account ID of the player (32-character hex string). The access token must belong to this same account. Get it from epicgames_userinfo_get (the sub claim). Example: 9626f441055349ce8cb7d7d5a483eaa2.
epicgames_ecom_entitlements_list
List ecom entitlements
epicgames_ecom_offers_list
List ecom offers
epicgames_ecom_ownership_check
Check ecom ownership
epicgames_friends_get
Get friends
epicgames_friends_list
List friends
epicgames_userinfo_get
Get userinfo
Build your Agent
Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Epic Games tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["epicgames"], toolNames: [
    "epicgames_userinfo_get",
    "epicgames_ecom_ownership_check",
    "epicgames_ecom_entitlements_list"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Check whether I own the Deluxe Edition and list my entitlements" }] });
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["epicgames"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Check whether I own the Deluxe Edition and list my entitlements" }],
  tools,
});

// Execute the tool call with the user's vaulted Epic Games OAuth token
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["epicgames"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Check whether I own the Deluxe Edition and list my entitlements" }],
  tools,
});

// Tool call runs with the user's vaulted Epic Games OAuth token
await sk.tools.executeTool(msg.content, "user_123");
import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["epicgames"] }, pageSize: 100,
});

const agent = new Agent({
  name: "gaming_agent",
  model: "gemini-2.5-pro",
  instruction: "Epic Games tools scoped to this user",
  tools,
});

await agent.run("Check whether I own the Deluxe Edition and list my entitlements");
Try these prompts
Copy any prompt into your agent. Each maps directly to a Epic Games tool. Click to copy, paste into your agent, done.
Profile and friends
Copy the prompt
Copied
What is my Epic Account ID?
Copy the prompt
Copied
List my Epic Games friends.
Copy the prompt
Copied
Which accounts have I blocked?
Entitlements
Copy the prompt
Copied
List the entitlements I hold in the Acme Arena sandbox.
Copy the prompt
Copied
Do I own the Deluxe Edition item?
Copy the prompt
Copied
Which consumable entitlements do I still hold?
Offers and social
Copy the prompt
Copied
Which offers are available to me in the Acme Arena sandbox?
Copy the prompt
Copied
Which offers have I already bought?
Copy the prompt
Copied
Show my friends and block list together.
SEE HOW AUTH WORKS
Each user signs in to Epic Games once, and Scalekit stores and refreshes their tokens. Credentials stay vaulted, every call is scope checked, and every action is logged.
1
Authorize
Your user connects
Epic Games
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Epic Games
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Epic Games
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Epic Games
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other media connectors.
Support and Ops Teams
Support ticket automation agent
Fetches new Zendesk tickets, drafts a reply from Notion knowledge base articles, digests what it cannot answer to Slack, and archives the rest, acting as the support agent rather than a shared API key.
Test other agents
See the same per-user auth pattern across other media connectors.
SUPPORT
Support ticket automation (Google ADK)
Fetch, annotate, and archive Zendesk tickets with Notion context, digesting anything it cannot answer to Slack.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Shared tokens break per-user analytics
A shared Epic Games token looks fine in a demo. In production every ownership check and friends lookup looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.
// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Epic Games today. Ten connectors tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access Epic Games as the user or through a shared service account?
As the user. Each user signs in to Epic Games once, and Scalekit stores and refreshes their tokens. Every lookup the agent makes is attributed to that player in your audit trail, not a shared service account.
Where is the Epic Games OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.
Can I limit what the agent does in Epic Games?
Yes. Filter by tool name in listScopedTools to expose only what you want, for example the friends tools without the Ecom tools. Every Epic Games tool is read-only, so the agent cannot change the player's account, friends, or purchases. Scalekit also enforces scope checks before every API call.
What happens when a user revokes Epic Games access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.
Which Epic Games tools need extra setup?
The friends and block list tools require the basic_profile and friends_list scopes. The Ecom tools, epicgames_ecom_entitlements_list, epicgames_ecom_offers_list, and epicgames_ecom_ownership_check, require the Ecom feature to be enabled on the OAuth client's client policy. epicgames_userinfo_get returns the Epic Account ID those tools need.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""epicgames"": {
""url"": ""https://mcp.scalekit.com/epicgames"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.epicgames]
url = ""https://mcp.scalekit.com/epicgames""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""epicgames"": {
""url"": ""https://mcp.scalekit.com/epicgames"",
""type"": ""http""
}
}
}