A side-by-side look at the Balatro Agent and Doom MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Balatro Agent for gaming work as a local process; choose Doom MCP for gaming as a local process. You can also run both side by side in one mcpServers block.
DOOM_WAD_PATH, DOOM_MCP_DEBUG.fire, use.Rows where the two servers differ are marked.
| Spec | B Balatro Agent | |
|---|---|---|
| Category | Gaming | Gaming |
| Quality signal | 48/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | DOOM_WAD_PATHDOOM_MCP_DEBUG |
| Verified owner | Community listing | Community listing |
| GitHub stars | 21 | 13 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View Balatro Agent | View Doom MCP |
No tool names declared yet. Check the project README from the listing page.
fireusePaste 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": {
"balatro-mcp": {
"command": "npx",
"args": [
"-y",
"balatro-mcp"
]
}
}
}
{
"mcpServers": {
"doom-mcp": {
"command": "npx",
"args": [
"-y",
"doom-mcp"
],
"env": {
"DOOM_WAD_PATH": "YOUR_DOOM_WAD_PATH_HERE",
"DOOM_MCP_DEBUG": "YOUR_DOOM_MCP_DEBUG_HERE"
}
}
}
}