Skip to main content
Glama
battle-training-mcp
by ciperx

Related Servers

Alternatives to battle-training-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      A 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.
      48
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides MCP tools to query Liquipedia esports data (matches, teams, players, tournaments, placements, standings) via the Liquipedia v3 API and MediaWiki action API.
      8
      56 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      14
      MIT

    TDQS

    B3.1/5.0

    Scored across 13 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues