Steam Trends API vs GameFork MCP

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

Which MCP Server Should You Choose?

S

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

Choose GameFork MCP 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).
• Primary tools included: search_games, post_game, update_game_metadata.

Explore GameFork MCP Details

Feature & Specification Comparison

Specification	S Steam Trends API Gaming	GameFork MCP Gaming
Summary	Steam concurrent player trends for any game over time. Free key at trendsapi.ai	Publish, fork, and improve runnable browser games — MCP for AI agents to post and contribute.
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": {
    "gamefork-mcp-2": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote"
      ]
    }
  }
}

Related MCP Server Comparisons