Steam Trends API vs Videogames

In-depth architectural comparison of the Steam Trends API and Videogames 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.

Which MCP Server Should You Choose?

Choose Steam Trends API 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).

Explore Steam Trends API Details

V

Choose Videogames when:

• You need dedicated capabilities in the Gaming domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: list_games, get_game, filter_games.

Explore Videogames Details

Feature & Specification Comparison

Specification	Steam Trends API Gaming	V Videogames Gaming
Summary	Steam concurrent player trends for any game over time. Free key at trendsapi.ai	Videogames MCP — wraps Free-to-Play Games API (freetogame.com, free, no auth)
Category & Scope	Gaming	Gaming
Quality signal

Tools & Capabilities Breakdown

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).

{
  "mcpServers": {
    "steam-trends-api-2": {
      "command": "uvx",
      "args": [
        "trendsapi-steam"
      ]
    }
  }
}

{
  "mcpServers": {
    "videogames": {
      "url": "https://pipeworx.io"
    }
  }
}

Related MCP Server Comparisons