Skip to main content
Glama
OnTarget600

epic-gog-free-games-mcp

by OnTarget600
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

epic-gog-free-games-mcp

A tiny, read-only Model Context Protocol server that reports free games on the Epic Games Store and GOG.com. No account, no credentials, no local filesystem access, no writes — it only calls public store endpoints.

Built for the lab's obot instance because no maintained, self-hostable Epic/GOG MCP exists (the commonly-cited pixfishx/mcp-epic-free-games was removed from GitHub and PyPI).

Tools

Tool

What it returns

epic_free_games_current

Games free to claim right now on the Epic Games Store (title, normal price, store URL, claim window, image).

epic_free_games_upcoming

The next Epic free games (with the date each becomes free). Unrevealed "Mystery Game" slots are returned with a null URL.

gog_giveaway

The current GOG giveaway (limited-time claim-and-keep), or {active:false} when none is running.

gog_free_games

Free / free-to-play titles from the GOG catalog (price = 0). These are permanently free / F2P, not giveaways. Demos excluded by default.

All tools take only optional args (country, limit, excludeDemos, countryCode, currencyCode). Nothing is required; the server installs and runs unconfigured.

Related MCP server: gamelibs-mcp

Data sources (all public, unauthenticated)

  • Epic: store-site-backend-static.ak.epicgames.com/freeGamesPromotions

  • GOG giveaway: www.gog.com/giveaway/api/get (404 = no active giveaway)

  • GOG catalog: catalog.gog.com/v1/catalog?price=between:0,0

Run it

Requires Node.js 20+ (uses global fetch).

npx github:OnTarget600/epic-gog-free-games-mcp     # stdio MCP server
# or, from a clone:
npm install && npm start
npm run selftest                                   # hit the live endpoints, print results

MCP client config (stdio)

{
  "mcpServers": {
    "epic-gog-free-games": {
      "command": "npx",
      "args": ["github:OnTarget600/epic-gog-free-games-mcp#v0.1.0"]
    }
  }
}

Security notes

  • Read-only. No tool mutates anything; there is no auth and no secret to leak.

  • Egress only to the three hosts above. No telemetry.

  • Store review/description text is third-party content — treat tool output as untrusted data, not instructions (standard prompt-injection hygiene).

  • Pin to a tag/commit (e.g. #v0.1.0) so a future push can't change behaviour silently.

License

MIT

Available Tools

4 tools
epic_free_games_currentA

List games that are FREE TO CLAIM right now on the Epic Games Store (limited-time, claim-and-keep). Returns title, description, normal price, store URL, claim window and image.

ParametersJSON Schema
NameRequiredDescriptionDefault
countryNoISO country code for pricing/availability (default US).US

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden. It indicates the tool is a read-only operation returning a list with time-sensitive claim windows. However, it does not explicitly state that it is safe and non-destructive, though implied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-structured sentence that conveys purpose, scope, and return content without any fluff. Every part earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with no output schema, the description covers the return fields well. However, it does not mention possible pagination or limits, though these may not be critical. Overall fairly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the only parameter 'country' is described in the schema. The description adds no additional meaning beyond the schema, thus baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'List', the resource 'games', and the specific context 'FREE TO CLAIM right now on the Epic Games Store'. It distinguishes from siblings like epic_free_games_upcoming by emphasizing 'right now' and adds return details.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implicitly distinguishes from epic_free_games_upcoming by using 'right now', but does not explicitly state when to use this tool versus siblings or provide exclusions. No mention of GOG alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

epic_free_games_upcomingA

List the NEXT free games coming to the Epic Games Store (announced upcoming giveaways), with the date each becomes free.

ParametersJSON Schema
NameRequiredDescriptionDefault
countryNoISO country code (default US).US

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided. Description says it lists games with dates, but does not disclose potential rate limits, pagination, data freshness, or output structure beyond 'date each becomes free'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, front-loaded with key information ('list the NEXT free games'), no unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with one optional parameter, the description covers the main purpose and what to expect (dates). Could hint at output format but overall sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only parameter 'country' is documented in schema with default and description. Tool description adds no extra meaning beyond what schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states it lists 'NEXT free games' on Epic Games Store with dates, clearly differentiating from 'current' giveaways and GOG siblings via naming and context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'NEXT free games' and mention of 'announced upcoming giveaways' implies using for future giveaways, distinct from current. No explicit when-not-to-use, but sibling names provide context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

gog_free_gamesA

List free / free-to-play games from the GOG catalog (price = 0). NOTE: these are permanently-free or F2P titles, not limited-time giveaways — use gog_giveaway for those. Demos are excluded by default.

ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoMax games to return, 1-48 (default 20).
excludeDemosNoFilter out titles containing 'Demo' (default true).
countryCodeNoISO country code (default US).US
currencyCodeNoCurrency code (default USD).USD

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations, so description carries full burden. It discloses that demos are excluded by default and the scope (permanent free, not giveaways). Could mention more about authentication or rate limits, but adequate for a simple list tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no fluff, front-loaded with core purpose and key distinction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, but description covers purpose, key limitations (permanent free only, demos excluded), and distinguishes from sibling. Lacks pagination or result details, but sufficient for a filter/list tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so schema already explains each parameter. Description adds minimal extra meaning beyond schema (e.g., 'excluded by default'), so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the tool lists permanently-free/F2P games from GOG with price=0, and distinguishes from gog_giveaway for limited-time giveaways.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use (for permanent free titles) and when not to (use gog_giveaway for giveaways), providing a clear alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

gog_giveawayA

Get the current GOG.com giveaway (a limited-time claim-and-keep game), if one is active. Returns {active:false} when there is no giveaway running.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden. It discloses the return value when no giveaway is active ({active:false}), but does not mention authentication, rate limits, or other behavioral traits. Adequate but minimal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose, no extraneous information. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters, no output schema, and simple behavior, the description is complete enough. It explains the return format. Could mention error cases or polling frequency, but not required for this basic tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist (0 params, 100% schema coverage), so baseline is 4. Description adds nothing beyond schema, but no parameter information is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Get the current GOG.com giveaway' with a specific verb and resource, and distinguishes from sibling tools like epic_free_games_current and gog_free_games by focusing on the limited-time claim-and-keep aspect.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use when checking for current giveaway, but does not explicitly state when to use this tool versus alternatives (e.g., for upcoming giveaways or other free games). No when-not-to-use or alternative tool names are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.3/5.0
Disambiguation5/5

Each tool targets a distinct combination of platform (Epic vs GOG) and type (current free, upcoming, permanently free, giveaway). No ambiguity between them.

Naming Consistency5/5

Names follow a consistent pattern: platform_descriptor, using snake_case and clear descriptive suffixes (current, upcoming, free_games, giveaway). Highly predictable.

Tool Count5/5

Four tools perfectly cover the core free game use cases for both stores. No excess or deficiency for this focused domain.

Completeness4/5

Covers all main free game scenarios: current and upcoming offers on Epic, permanently free and limited-time giveaways on GOG. Minor gap: no history of past giveaways, but that's outside the typical scope.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • discord-py-self-mcp

    xeophon
    A
    license
    Not graded
    quality
    C
    maintenance
    Read-only MCP server for Discord that lists guilds, channels, and reads or searches messages using a self-bot account via discord.py-self.
    MIT

  • gamelibs-mcp

    AliSoftware
    A
    license
    A
    quality
    B
    maintenance
    An MCP server that exposes your Steam, Epic Games Store, and IGDB game data as tools, enabling game library queries, install status checks, and metadata enrichment.
    12
    2
    MIT

  • Discord MCP

    JoelBChapmanII
    F
    license
    A
    quality
    C
    maintenance
    Local, read-only MCP server that connects to Discord via REST API, allowing listing guilds, channels, and messages with strict access controls and no write operations.
    5

  • komga-mcp

    pierrec18
    A
    license
    Not graded
    quality
    B
    maintenance
    A read-only MCP server that exposes Komga reading data via Streamable HTTP, providing tools for searching comics, listing unread series, and tracking reading progress.
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OnTarget600/epic-gog-free-games-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server