A side-by-side look at the Bungie and Guild Wars 2 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 Guild Wars 2 for gaming as a local process. You can also run both side by side in one mcpServers block.
PLATFORM_BUNGIE_KEY.DestinyInventoryItemDefinition.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Gaming | Gaming |
| Quality signal | 52/100 · Good | 43/100 · Fair |
| 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_BUNGIE_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 1 | Not listed |
| Full listing | View Bungie | View Guild Wars 2 |
DestinyInventoryItemDefinitionNo tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"bungie": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-bungie"
],
"env": {
"PLATFORM_BUNGIE_KEY": "YOUR_PLATFORM_BUNGIE_KEY_HERE"
}
}
}
}
{
"mcpServers": {
"guild-wars-2": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-guild-wars-2"
]
}
}
}