Skip to main content
Glama
deanxizian

balatro-codex-mcp

by deanxizian

Related Servers

Alternatives to balatro-codex-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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

    TDQS

    A3.5/5.0

    Scored across 18 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues