Chess vs Steam Trends API

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

C

Choose Chess 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: get_player, get_stats, get_games.

Explore Chess Details

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

Feature & Specification Comparison

Specification	C Chess Gaming	Steam Trends API Gaming
Summary	Chess.com MCP — wraps the Chess.com public API (free, no auth)	Steam concurrent player trends for any game over time. Free key at trendsapi.ai
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": {
    "chess": {
      "url": "https://pipeworx.io"
    }
  }
}

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

Related MCP Server Comparisons