balatro-codex-mcp
Related Servers
Alternatives to balatro-codex-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables users to read compact game state, execute legal actions with freshness checks, and inspect action schemas and wiki details for the Steam version of Balatro through MCP tools.MIT
- AlicenseAqualityBmaintenanceWindows-local MCP for Steam Balatro: tool-calling AI reads player-visible state, chooses and executes native actions, confirms results, and saves local experience. Glama's Linux sandbox can introspect MCP and run game-independent tools such as calculate, but cannot connect to Balatro on the user's Windows machine. Without the local game, health reports disconnected.124MIT
- AlicenseAqualityCmaintenanceLets LLMs play a local Slay the Spire 2 installation by exposing game state, action help, and 29 gameplay actions through STDIO tools, with waiting, wiki lookups, and profile inspection.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients and external AI supervisors to oversee and steer native Codex sessions through a thin local stdio bridge. It exposes eleven codex_* supervisory tools for tasks such as listing threads, starting turns, observing progress, steering, responding to approvals, interrupting, checkpointing, and rolling over work.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Codex to control a DeSmuME WebAssembly emulator for Nintendo DS games, including state management, screenshots, and persistent scripting via stdio MCP.MIT
- AlicenseAqualityBmaintenanceEnables ChatGPT or other MCP clients to control native Codex sessions on Windows, providing tools for thread management, turns, observation, steering, and responding to approvals.744MIT
TDQS
Scored across 18 tools
Most tools map to distinct game actions (play/discard, buy/reroll, etc.), so there is little confusion. The only slight overlap is among the informational tools (get_state, available_actions, capabilities), which all provide state/action data but serve different purposes.
All tools share the 'balatro_' prefix and use snake_case. Most follow a verb_noun pattern, but a few (health, capabilities, available_actions, next_round) are noun-like, creating minor inconsistency. Overall, the naming is still predictable and readable.
With 18 tools, the set is slightly above the ideal 3-15 range, but each tool corresponds to a specific part of the Balatro game cycle. The count feels justified for the game's complexity, though a few informational tools could potentially be consolidated.
The tool set covers the entire game loop: starting a run, selecting/skipping blinds, playing/discarding cards, using consumables, choosing/skipping packs, shop interactions, rearranging, cashing out, and moving to the next round. Informational tools (state, health, capabilities, available actions) fill any remaining needs, leaving no significant dead ends.