Skip to main content
Glama
Sign In
Slay the Spire 2 MCP

Slay the Spire 2 MCP

by Isendoum
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to Slay the Spire 2 MCP

No user-submitted related servers found.

    Related Servers

    • balatro-agent

      KaishenChiang
      A
      license
      A
      quality
      B
      maintenance
      Windows-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.
      4
      12
      3
      MIT

    • sts2-mcp-bridge

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

    • STS2 AI Agent

      CharTyr
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to play Slay the Spire 2 by exposing game state and actions through an MCP server, supporting combat, rewards, and run management.
      357
      -

    • DD1-Copilot

      FengJPC
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agent-controlled Darkest Dungeon gameplay by providing game state, tactical context, validated semantic actions, and persistent campaign memory to AI assistants.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources