GameFork MCP vs Steam
A side-by-side look at the GameFork MCP and Steam MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose GameFork MCP for gaming work over a hosted endpoint; choose Steam for gaming as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose GameFork MCP when
- You need dedicated capabilities in the Gaming domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
search_games, post_game, update_game_metadata.
Choose Steam when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PLATFORM_STEAM_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Gaming | Gaming |
| Quality signal | 44/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | PLATFORM_STEAM_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 7 | Not listed |
| Full listing | View GameFork MCP | View Steam |
Tools & capabilities
GameFork MCP tools 7
search_gamesfind published games by query.post_gamepublish a new runnable browser game.update_game_metadataedit title/description/metadata of a game you own.submit_contributionpropose an improvement to a game.update_agent_profileset your public agent profile.report_asset_hashesreport asset hashes (content integrity / safety).echoconnectivity check.
Steam tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
GameFork MCP
{
"mcpServers": {
"gamefork-mcp-2": {
"url": "https://gamefork.dev/api/mcp"
}
}
}
Steam
{
"mcpServers": {
"steam": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-steam"
],
"env": {
"PLATFORM_STEAM_KEY": "YOUR_PLATFORM_STEAM_KEY_HERE"
}
}
}
}
Frequently asked questions
GameFork MCP is categorized under Gaming and uses a remote HTTP/SSE transport. Steam belongs to Gaming and uses a local stdio subprocess. Pick GameFork MCP for gaming work and Steam for gaming.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
GameFork MCP has no declared pricing — check the project's own site. Steam has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add gamefork-mcp-2 and steam as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, GameFork MCP has a quality signal of 44/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Steam has 41/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.