Steam vs Vibe MCP
A side-by-side look at the Steam and Vibe MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Steam for gaming work as a local process; choose Vibe MCP 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 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. - You want tools like
resolve_vanity_url, player_summary, player_summaries.
Choose Vibe MCP when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
VIBE_API_URL, VIBE_EXTRAS. - You want tools like
vibe_start, vibe_init, vibe_who.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Gaming | Gaming |
| Quality signal | 60/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | PLATFORM_STEAM_KEY | VIBE_API_URLVIBE_EXTRAS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 14 | 9 |
| Full listing | View Steam | View Vibe MCP |
Tools & capabilities
Steam tools 14
resolve_vanity_urlVanity URL → SteamID64.player_summaryFetch public Steam profile for a single SteamID64: persona name, avatar, profile URL, country, last logoff, visibility status.player_summariesFetch public Steam profiles for up to 100 comma-separated SteamID64s in one request; returns persona name, avatar, country, and status for each.friend_listList a Steam user's friend list by SteamID64; optionally filter by relationship type (friend or all). Returns array of SteamID64s and relationship status.owned_gamesList all games owned by a SteamID64; optionally include app name/icon and free-to-play games. Returns appid, playtime_forever (minutes), and per-game metadata.recently_playedList games played by a SteamID64 in the last two weeks, with playtime in the last 2 weeks and total playtime. Optional count caps results.player_achievementsAchievements for a game.player_statsUser stats for a game.player_levelReturn the Steam Community level (integer) for a given SteamID64.player_bansCheck VAC ban, community ban, and economy ban status for one or more comma-separated SteamID64s. Returns CommunityBanned, VACBanned, NumberOfVACBans, DaysSinceLastBan.app_newsApp news feed.app_detailsStore page detail (Steam Store API).- +2 more on the listing page
Vibe MCP tools 9
vibe_startEntry point — authenticates, shows presence, checks inboxvibe_initSet up your identity (GitHub OAuth)vibe_whoSee who's online and what they're buildingvibe_dmSend a direct messagevibe_inboxCheck your unread messagesvibe_statusSet your mood (shipping, thinking, debugging, etc.)vibe_shipShare what you shippedvibe_discoverFind people building similar thingsvibe_helpShow available commands
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.
Steam
{
"mcpServers": {
"steam": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-steam"
],
"env": {
"PLATFORM_STEAM_KEY": "YOUR_PLATFORM_STEAM_KEY_HERE"
}
}
}
}
Vibe MCP
{
"mcpServers": {
"vibe-mcp": {
"command": "npx",
"args": [
"-y",
"slashvibe-mcp"
],
"env": {
"VIBE_API_URL": "YOUR_VIBE_API_URL_HERE",
"VIBE_EXTRAS": "YOUR_VIBE_EXTRAS_HERE"
}
}
}
}
Frequently asked questions
Steam is categorized under Gaming and uses a local stdio subprocess. Vibe MCP belongs to Gaming and uses a local stdio subprocess. Pick Steam for gaming work and Vibe MCP 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.
Steam has no declared pricing — check the project's own site. Vibe MCP 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 steam and vibe-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Steam has a quality signal of 60/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Vibe MCP has 53/100 (Good) with 3 views, 0 installs and 0 GitHub stars.