Slay the Spire 2 MCP
Related Servers
Alternatives to Slay the Spire 2 MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceWindows-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.412MIT
- AlicenseNot gradedqualityBmaintenanceEnables an MCP agent to observe and command Slay the Spire 2 game state via HTTP, and optionally autopilot combat with a local deterministic policy, without LLM in the critical path.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to play Slay the Spire 2 by exposing game state and actions through an MCP server, supporting combat, rewards, and run management.339-
- FlicenseNot gradedqualityCmaintenanceEnables AI-assisted gameplay for Slay the Spire by reading game state and providing strategy advice or automated actions via Claude Code.1-
- AlicenseNot gradedqualityBmaintenanceEnables agent-controlled Darkest Dungeon gameplay by providing game state, tactical context, validated semantic actions, and persistent campaign memory to AI assistants.MIT
- AlicenseBqualityBmaintenanceGives LLMs a genuine in-game seat in Civilization V, letting them scout, settle, negotiate, fight, and manage a civilization through tool calls with the same fog-of-war information a human player sees.144MIT
TDQS
Scored across 7 tools
Most tools are clearly distinct: state reading (get_game_state), action discovery (get_action_help), acting (take_action), waiting (wait_for_player), and reference lookups (search_wiki, get_profile) target different needs. The descriptions explicitly clarify the tricky boundary between get_action_help (syntax) and get_game_state (actual choices), though health_check and get_game_state overlap slightly since both report game status.
All tools use consistent snake_case with clear verb_noun or verb_object patterns (get_game_state, take_action, search_wiki, wait_for_player). The get_* family is predictable and no casing or verb-style mixing appears.
Seven tools is well-scoped for an agent-driven game controller, covering status, read, help, act, wait, and profile/reference lookups without redundancy. Each tool earns its place in the gameplay loop.
The core agent loop (health, state, help, action, wait) plus profile/wiki lookups is well covered. Minor gaps exist around save/load, restart, or deck-management operations, but these are workable given the bridge exposes actions through take_action.