Token Bowl MCP Server
Related Servers
Alternatives to Token Bowl MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables AI agents to access Sleeper fantasy football league data, rosters, matchups, projections, waivers, trends, and league chat, with read-only safety and optional authorized chat posting.26MIT
- AlicenseBqualityBmaintenanceEnables reading Sleeper fantasy football rosters, matchups, standings, news, chat, and pick'em entries, with optional write actions for setting lineups, claiming waivers, and proposing trades.391MIT
- FlicenseAqualityDmaintenanceEnables natural language interaction with Sleeper Fantasy Football API data, allowing queries about leagues, players, matchups, draft results, and trade analysis.1325-
- AlicenseNot gradedqualityBmaintenanceEnables AI models to manage and query fantasy sports leagues through the Sleeper API, supporting tasks like player lookups, league activity, and draft management.129 npmMIT
- FlicenseAqualityBmaintenanceEnables access to Sleeper fantasy football data, including users, leagues, rosters, matchups, transactions, drafts, and player information.13215 npm-
- AlicenseAqualityDmaintenanceProvides read-only access to the Sleeper Fantasy Sports API for league info, rosters, matchups, drafts, transactions, and player data.18129 npm1MIT
TDQS
Scored across 48 tools
Most tools target distinct operations, but several overlap: search vs search_players_by_name vs get_waiver_wire_players (with search_term) all find players, get_league_transactions vs get_recent_transactions split transaction retrieval, get_waiver_wire_players vs get_waiver_analysis both surface waiver candidates, and get_user vs get_league_users differ only subtly. Descriptions help, but an agent could easily misselect among these.
Fantasy-football tools use a consistent snake_case get_/search_/fetch pattern, and chat tools are internally consistent with a token_bowl_chat_ prefix. However, the two halves use entirely different conventions (no prefix vs verbose prefixed), and verbs vary (get, search, fetch, evaluate, health_check), giving a mixed but readable overall scheme.
With 48 tools split across fantasy-football data (23) and a full chat subsystem (25, including 7 admin tools), the surface is heavily over-provisioned. The chat group alone exceeds the 'heavy' 16-25 range, and many fine-grained variants (unread vs read, room vs direct) inflate the count.
The fantasy-football surface is thorough (league settings, rosters, matchups, transactions, drafts, traded picks, playoffs, player stats, trending, waivers, schedule), and the chat surface covers messaging, profiles, unread management, and admin CRUD. The main gap is the lack of any write/mutation operations for league actions (lineup setting, adds/drops, trades), which limits the lifecycle to read-mostly workflows.