Bungie vs Videogames
A side-by-side look at the Bungie and Videogames MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Bungie for gaming work as a local process; choose Videogames 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 Bungie when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
PLATFORM_BUNGIE_KEY. - You want tools like
manifest, search_destiny_player, search_destiny_players_by_global_name.
Choose Videogames when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
- You want tools like
list_games, get_game, filter_games.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Gaming | Gaming |
| Quality signal | 61/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | PLATFORM_BUNGIE_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 13 | 3 |
| Full listing | View Bungie | View Videogames |
Tools & capabilities
Bungie tools 13
manifestDestiny 2 manifest metadata.search_destiny_playerFind Destiny player by display name with code.search_destiny_players_by_global_namePaginated global search for Destiny players by Bungie name prefix; returns membershipId, membershipType, and bungieName for matching accounts.profileProfile + characters + inventory.characterFetch Destiny 2 character data for a specific character by membership_type, destiny_membership_id, and character_id; components controls which data blocks (e.g. 200=characters, 205=equipment) are returned.linked_profilesFetch all cross-platform Destiny 2 profiles linked to a Bungie.net membership_id/membership_type; optionally return all memberships including inactive ones.clanClan/group detail.clan_membersClan members.user_by_idLook up a Bungie.net user and their Destiny memberships by membership_id and membership_type; returns displayName, bungieNetUser, and destinyMemberships.equipped_loadoutEquipped loadout (components=205).historical_statsFetch historical Destiny 2 stats (kills, deaths, KD, wins) for a character or account (character_id=0) filtered by activity modes (comma-separated mode IDs).historical_stats_for_accountFetch account-wide aggregated Destiny 2 historical stats across all characters for a membership_type + destiny_membership_id.- +1 more on the listing page
Videogames tools 3
list_gamesList free-to-play games from FreeToGame, optionally filtered by platform (pc/browser) and category (e.g., mmorpg, shooter, strategy) and sorted by release-date, popularity, or alphabetical. Returns all matching games.get_gameGet full details for a free-to-play game by its FreeToGame ID. Returns title, description, genre, platform, publisher, developer, release date, screenshots, and minimum system requirements.filter_gamesFilter free-to-play games on FreeToGame by a dot-separated tag combination (e.g., "3d.mmorpg.fantasy", "shooter.pvp") and optional platform (pc/browser). Returns matching games with title, genre, platform, and release date.
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.
Bungie
{
"mcpServers": {
"bungie": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-bungie"
],
"env": {
"PLATFORM_BUNGIE_KEY": "YOUR_PLATFORM_BUNGIE_KEY_HERE"
}
}
}
}
Videogames
{
"mcpServers": {
"videogames": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-videogames"
]
}
}
}
Frequently asked questions
Bungie is categorized under Gaming and uses a local stdio subprocess. Videogames belongs to Gaming and uses a local stdio subprocess. Pick Bungie for gaming work and Videogames 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.
Bungie is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Videogames 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 bungie and videogames as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Bungie has a quality signal of 61/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Videogames has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.