bb-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BB_PAT | Yes | BuzzerBeater Personal Access Token (PAT), created in the game under Settings → API & third-party apps → Personal tokens |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Read-only wrapper around the BuzzerBeater public API. Call get_me first to learn your team ids and granted scopes. Own-club tools (training, staff, facilities, economy) need the matching token scope; other clubs return 403. Generally speaking prefer few, targeted calls and do not crawl other clubs or players. Useful for analyzing the roster of your own team (to suggest tactics and training plans) and other teams (for scouting or counter-tactics), for analyzing players for sale and how they fit in your roster, or get generic information about teams, players, national teams and everything related to BuzzerBeater.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_team_trainingC | Current training drill and positions of your own team. |
| get_team_training_historyB | Results of past training sessions (skill upgrades and such) of your own team. Non-supporters get the latest session only. |
| get_team_staffC | Staff in your own team: role, level, specialty, salary. |
| get_team_facilitiesB | Building available for your own team: levels, max level and weekly upkeep. |
| get_team_economyB | Economy recap of your own team. Balance, available money, expected sale proceeds and transactions. |
| get_team_salariesB | Weekly player and staff salaries of your own team. |
| get_arena_attendanceC | Info about your own arena. Attendance, prices and gate revenue, newest first. |
| get_teamC | A summary of a club: name, country, manager, league, arena, record. |
| get_team_rosterA | Give the complete roster of a team. For your own team, you also get the skill values, otherwise you'll get only the public information (name, age, DMI, game shape) |
| get_team_scheduleD | A club schedule, oldest info come first. |
| get_team_statsC | Team statistics for a season. You can get more details with "mode" parameter equal to "Totals". |
| get_team_arenaC | Public information about a team arena (seats and prices). |
| get_meA | Current manager: username, supporter flag, owned clubs, coached national teams, granted scopes. Start here for team ids. |
| search_market_playersA | Search the transfer list with players currently on sale. It does not returns skills, but only public information. Use to scout the market and get a glimpse of what could be a good player(s) based on the request made. More details of a single player can be received via tool get_auction. filters keys (PascalCase): Min/Max + Age, Height, Salary, Price, Overall, Potential, Experience, GameShape, JumpShot, JumpRange, OutsideDefense, Handling, Driving, Passing, InsideShot, InsideDefense, Rebound, ShotBlock, FreeThrow; plus Country, Position, SecondPosition, Injury (Nothing|OnlyInjured|ExcludeInjured), OnNationalTeam. Level-valued filters (skills, Experience, GameShape) take names like Average, Strong, Prolific, Legendary. More than four skill bounds needs a supporter; eight is the maximum. order_by e.g. AuctionTime, Age, Salary, CurrentBid, Overall, Potential. Searches go at most 150 deep, up to 30 per page. |
| get_auctionA | Auction of a listed player. Includes more details then what received with search_market_players, including player skills. Use it when the user asks for a player on sale and to compare it with the current people in team. Avoid to abuse of this call for crawling for players. Better filter with search_market_players first in case. |
| get_matchB | Match header: teams, date, competition, score by period. Box score is not included until the match is overnds. |
| get_boxscoreB | Box score: strategies, ratings, every player's line. Can be received only after the match is over. |
| get_match_eventsA | One page (up to 200) of play-by-play for a finished match.
Request is paginated with a cursor, pass |
| get_playerB | Player page. Includes only public information (age, name, potential, game shape, DMI, etc) and skills only for your own players. |
| get_player_trainingA | Training sessions of your own player. Require a supporter subscription, or info won't be returned to you. |
| scout_teamA | Scout a club's tactics over its recent games. Use only when explicitly asked to scout a team.
Give |
| get_match_shootingA | Shot zones and per-player attempts for a finished match. Use only when explicitly asked for a detailed analysis of a team. |
| get_standingsB | Standings table per group of each stage of a BuzzerBeater competition. |
| get_seasonsC | Seasons, oldest first. |
| get_countriesC | Every country available in BuzzerBeater. |
| get_country_leaguesB | Leagues of a country. |
| get_country_national_teamsC | Senior and junior national teams of a country, with coaches. |
| get_national_team_rosterC | Called-up squad of a national team. Skills only for the coach. |
| get_national_team_training_historyA | Squad skill changes from club training of players included in a National team, newest first. Works only for coaches/assistant of said national team, otherwise the request will fail. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 29 tools
Most tools target a distinct resource+action, and descriptions clarify the fine distinctions (e.g. get_arena_attendance vs get_team_arena vs get_team_facilities, or get_team_training vs get_team_training_history). The riskiest overlaps are the analytics cluster (get_team_stats, scout_team, get_match_shooting, get_boxscore) and get_team_roster vs get_player, but the "use only when explicitly asked" guidance mitigates misselection.
Nearly everything follows a snake_case verb_noun pattern (get_*, search_*, scout_*). The one wrinkle is that the get_team_* prefix is overloaded: some of those tools operate on any club (roster, schedule, stats, arena) while others are own-team-only (training, staff, facilities, economy, salaries), and get_arena_attendance sits outside that prefix.
29 tools is heavy for a single server and pushes past the comfortable 3-15 range. The domain is genuinely broad (teams, players, market, matches, competitions, countries, national teams) so most tools do map to unique data, but sub-resources like facilities/economy/salaries/staff could plausibly be consolidated into a team-finances or team-info call.
Coverage of the read surface is strong: team info/roster/schedule/stats/training/finances, market search plus auction detail, match header/boxscore/events/shooting, standings, seasons, countries, leagues and national teams. Notable gaps remain on the player side (no season-by-season player stats or player career/history, no transfer/bid actions) and no league-level fixture listing, but these are minor for a read-only companion API.