battle-training-mcp
Related Servers
Alternatives to battle-training-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI coding agents to query battle.training ladders, cup standings, bot profiles, live matches, meta, rules, and replays; simulate controllers locally; and, with an API key, manage bots and cup entries.16MIT
- AlicenseAqualityDmaintenanceEnables AI agents to run battles, tournaments, and analyze strategies in the Battle Arena game programmatically.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to register, submit signed scores, and query leaderboards and profiles on the FloweringAgents performance registry via MCP tools.MIT
- AlicenseBqualityDmaintenanceA local MCP server that exposes the SAIR Competition Public API as tools for MCP clients, enabling account introspection, competition browsing, submissions, playground operations, cheatsheet management, and Contributor Network interactions.48MIT
- AlicenseAqualityDmaintenanceProvides MCP tools to query Liquipedia esports data (matches, teams, players, tournaments, placements, standings) via the Liquipedia v3 API and MediaWiki action API.856 npmMIT
- AlicenseAqualityBmaintenanceEnables local MCP-capable agents to read-only query Zhangchui's already-published Warhammer 40K reports, matchups, army rosters, and statistical definitions over a fixed-route HTTPS public API, without admin accounts, SSH, or database credentials. It exposes six tools for listing and fetching reports, matchups, rosters, and data notes, with release-ID pinning, pagination, and explicit handling of unprepared or unavailable data.14MIT
TDQS
Scored across 13 tools
Most tools have clear, distinct purposes across setup, rules, ladders, matches, bots, and cups. The main ambiguity is between get_ladder and list_ladders, and to a lesser extent get_cup versus list_ladders, since both concern ladder/cup listings.
The set mostly follows a readable snake_case verb_noun pattern such as get_rules, list_matches, create_bot, upload_version, and enrol_cup. The main deviation is whoami, and the get_ladder/list_ladders pair is slightly inconsistent in using get versus list for related concepts.
With 13 tools, the set is well within a reasonable range for a domain involving setup, rules, matches, bots, leaderboards, and cups. Each tool appears to serve a distinct part of the workflow without excessive surface area.
The surface covers the core lifecycle: onboarding, rules, starter code, matches, ladders, bot creation, version upload, and cup enrolment. Minor gaps exist around bot administration, such as updating or deleting a bot, and cup participation lacks an explicit unenrol operation.