Skip to main content
Glama

Related Servers

Alternatives to battle-training-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Exposes the battle.training agent tank arena API as MCP tools, letting clients read ladder standings, bot ratings, recent matches and replay URLs, and inspect cup info. With an API key it also enables registering bots, uploading smoke-tested controller versions, and enrolling in sponsored cups.
      13
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets AI assistants download competition training and inference data, submit predictions, backtest strategies on the meta-model, and check performance through natural language. It can be used as a hosted endpoint or run locally with an API key.
      1,120 PyPI
      9
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Enables 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
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI assistants with access to real-time Brawl Stars game data including player statistics, club information, brawler details, battle logs, and current events through the Brawl Stars API.
      16 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables remote access to arcade game play, rules, challenges, leaderboards, and public AI profiles through Streamable HTTP.
      AGPL 3.0

    TDQS

    B3.2/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools map to a distinct resource: ladder, cup, bot profile, match, live, meta, rules, docs, replay, simulate, plus three write operations. The main soft spots are the family of standings tools (battle_ladder vs battle_cup vs battle_agents) and the status/docs/rules trio, where an agent must read descriptions carefully to pick correctly, though the descriptions do differentiate them by scope.

    Naming Consistency4/5

    Every tool carries the same battle_ prefix, and names are either a clean resource noun (battle_ladder, battle_bot, battle_replay) or verb_noun for actions (battle_create_bot, battle_upload_version, battle_enrol_cup). The mix of bare-noun read tools and verb_noun write tools is a readable, minor deviation rather than a real inconsistency.

    Tool Count4/5

    16 tools is slightly above the comfortable range but each covers a genuinely different facet of the domain (ladder, match, replay, simulation, account writes, docs). Nothing looks like filler, so the size is justified rather than bloated.

    Completeness3/5

    The surface covers read/analyse/simulate plus the core account lifecycle (create bot, upload version, enrol cup), which is strong. However, cups can only be fetched by slug with no tool to list available cups or theaters, and there is no way to delete/rename a bot or retire a version, leaving a couple of dead ends an agent would hit.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues