sts1
Related Servers
Alternatives to sts1
No user-submitted related servers found.
Related Servers
- 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.357-
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseAqualityCmaintenanceEnables any local AI agent to play turn-based games over MCP by exposing reset, observe, and act verbs with structured observations and validated legal actions.6MIT
- AlicenseBqualityBmaintenanceAn MCP server that enables AI agents to play Library of Ruina by reading game state, navigating UI, fighting battles, and selecting emotion cards.232MIT
- AlicenseNot gradedqualityBmaintenanceThis server enables MCP clients to control a real Minecraft Java player client with native first-person gameplay, structured spatial perception, bounded continuous actions, and optional livestream widgets.2MIT
- AlicenseAqualityBmaintenanceEnables AI clients to read and control Civilization VI game state through FireTuner, execute actions, enforce turn-completion checks, and retain long-term strategy context. Supports a shared local HTTP connection so multiple MCP clients can use one game connection.99MIT
TDQS
Scored across 12 tools
Most tools target clearly distinct actions (play_card, end_turn, choose, confirm, leave), but send_command duplicates nearly every dedicated tool and run_turn overlaps with play_card/end_turn, creating some selection ambiguity. The descriptions explicitly guide agents to prefer dedicated tools, which mostly resolves the confusion.
All names are snake_case and verb-first, with most following a verb_noun pattern (get_game_state, play_card, run_turn, flush_observations). A few are bare verbs (proceed, choose, confirm, cancel, leave), which is a minor deviation from a single predictable pattern.
12 tools is well within the sweet spot for this domain. The set covers combat actions, screen navigation, turn automation, state retrieval, and observation logging without obvious bloat, and each tool appears to earn its place.
Core gameplay (playing cards, ending turns, choosing options, confirming, cancelling, leaving) and autonomous turn execution are covered, with send_command as a raw fallback. However, common actions like potion usage lack a dedicated convenience tool and must go through send_command, leaving a minor gap.