Sea of Fox RTS MCP
Related Servers
Alternatives to Sea of Fox RTS MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables an LLM agent to play a melee match against the game's built-in AI by exposing raw wc3env orders as MCP tools, with games graded and native replays saved.Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to connect to and control a windowed copy of Romance of the Three Kingdoms IX with Power Up Kit, letting them observe the game UI, gather officer/city intelligence, issue facility/transport commands, and advance turns through exposed MCP tools.-
- FlicenseAqualityDmaintenanceEnables AI assistants such as Trae or Claude to control StarCraft 1.16.1 matches through BWAPI, providing tools to read game state, train units, build, move, attack, gather, and chat.9-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read and control Command: Modern Operations scenarios locally via MCP tools, supporting real-time battle assessment, task planning, and scenario editing.11MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI clients to register agent identities, discover and join social strategy matches, negotiate, submit game actions, and review post-match autopsies and leaderboards.MIT
- AlicenseAqualityCmaintenanceEnables MCP-compatible AI agents to play full Civilization VI games by reading game state and issuing rule-enforced actions such as moving units, managing cities, conducting diplomacy, and ending turns.76MIT
TDQS
Scored across 5 tools
Each tool occupies a clearly separate lane: rts_order writes actions, rts_observe reads dynamic match state, rts_catalog reads static faction/economy rules, rts_build_sites answers a narrow placement query, and rts_wait blocks on a condition. The only mild adjacency is that rts_wait returns a fresh overview like rts_observe, but its condition/timeout semantics make the boundary obvious.
All tools share a uniform rts_ prefix with short, snake_case suffixes, so the set reads as one family. The suffixes mix verb-style (observe, wait, order) with noun-style (catalog, build_sites), which is a minor stylistic deviation rather than a real inconsistency.
Five tools is well-scoped for an agent-facing RTS interface: each tool absorbs a coherent, multiplexed capability (batched orders, multi-mode observation) instead of exploding into dozens of narrow calls. No tool looks vestigial, and none is doing two unrelated jobs.
The surface covers the core loop: discover rules/costs, observe state, locate legal build sites, issue validated orders, and await outcomes, with an idempotent batchId recovery path. Gaps are minor (e.g. no explicit tool for resigning, chat/diplomacy, or inspecting rejected-order details beyond the order response), and agents can work around them.