balatro-codex-mcp
Related Servers
Alternatives to balatro-codex-mcp
No user-submitted related servers found.
Related Servers
- 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 gradedqualityBmaintenanceEnables Codex to control a DeSmuME WebAssembly emulator for Nintendo DS games, including state management, screenshots, and persistent scripting via stdio MCP.MIT
- AlicenseAqualityAmaintenanceEnables ChatGPT or other MCP clients to control native Codex sessions on Windows, providing tools for thread management, turns, observation, steering, and responding to approvals.738MIT
- AlicenseNot gradedqualityCmaintenanceEnables Codex to operate your already-open Firefox tabs via local MCP tools for status, tab management, navigation, interaction, and screenshots on Windows x64 with Firefox 140+.AGPL 3.0
- FlicenseNot gradedqualityCmaintenanceEnables MCP-compatible hosts such as OpenCode to drive the Codex CLI through codex app-server over stdio, exposing tools to run prompts, inspect status, list threads, and interrupt running turns.-
- AlicenseBqualityCmaintenanceAllows Codex to launch Tuanjie projects and interact with editor scenes, GameObjects, scripts, assets, and console via the Codely Bridge, exposing 22 MCP tools.22MIT
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.