In-depth architectural comparison of the Gaming Feeds and Steam Trends MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Gaming Feeds
Gaming · Local stdio
Quality: 48/100 (Fair) | Auth: No auth required
Steam Trends MCP
Gaming · Remote HTTP/SSE
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Gaming Feeds if you need specialized Gaming tools running via a local process. Choose Steam Trends MCP if your workspace requires Gaming integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Gaming Feeds when:
You need dedicated capabilities in the Gaming domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
List the curated gaming feeds (id, title, category, source). Optionally filter by category (gaming) or keyword. Pass an id to read_feed.
read_feed
Read a curated gaming feed by its id (from list_feeds). Returns normalized items (title, link, published, summary). Optionally filter items by keyword.
fetch_feed
Fetch and normalize any RSS / Atom / RDF feed by URL. CF-robust: fetches directly and falls back to a proxy if the source blocks the gateway. Use list_feeds first for curated sources.
Steam Trends MCP Tools (3)
get_time_series
Weekly (or daily) history for **one** `source` + `keyword`. Same name on MCP and REST (`mode: "get_time_series"`). REST also accepts `get_trends` as an alias.
get_growth
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Gaming Feeds is categorized under Gaming and uses a local stdio subprocess. In contrast, Steam Trends MCP belongs to Gaming using remote streaming HTTP/SSE transport. Select Gaming Feeds when you need capabilities focused on gaming and Steam Trends MCP when you require tools for gaming.
Point-to-point percent change. Several windows in one call still count as **one** request for that source + keyword.
get_top_trends
Live ranked list. **No keyword.** On MCP, `type` is required and must match the feed name **exactly** (including capitals). On REST, omit `type` only if you intend to pull every feed (billed per feed).