
Wraps the FreeToGame.com API to pull data on free-to-play games without requiring authentication. The source doesn't list specific tools, but you'd expect operations like searching games, filtering by genre or platform, and fetching game details. Part of the Pipeworx gateway ecosystem, which lets you either use this standalone endpoint or connect to their unified gateway for access to 600+ data sources. Includes an ask_pipeworx tool that handles natural language queries instead of direct tool calls. Reach for this when you're building gaming recommendations, cataloging F2P titles, or need quick game metadata without API keys or rate limit hassles.
Videogames MCP — wraps Free-to-Play Games API (freetogame.com, free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
list_games | List free-to-play games from FreeToGame, optionally filtered by platform (pc/browser) and category (e.g., mmorpg, shooter, strategy) and sorted by release-date, popularity, or alphabetical. Returns all matching games. |
get_game | Get full details for a free-to-play game by its FreeToGame ID. Returns title, description, genre, platform, publisher, developer, release date, screenshots, and minimum system requirements. |
filter_games | Filter free-to-play games on FreeToGame by a dot-separated tag combination (e.g., "3d.mmorpg.fantasy", "shooter.pvp") and optional platform (pc/browser). Returns matching games with title, genre, platform, and release date. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"videogames": {
"url": "https://gateway.pipeworx.io/videogames/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/videogames/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Videogames data" })
The gateway picks the right tool and fills the arguments automatically.
MIT