Yahoo Fantasy Baseball MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YF_CLIENT_ID | No | Your Yahoo OAuth client ID | |
| YF_CLIENT_SECRET | No | Your Yahoo OAuth client secret |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fantasy_get_preferencesA | Get the locally saved default Yahoo league and team for browser-driven workflows. This does not inspect Yahoo or verify that the browser is signed in. |
| fantasy_set_default_teamA | Save a Yahoo league and team discovered from the signed-in browser. This stores local identifiers only and does not call Yahoo. |
| analyze_player_statsA | Fetch and aggregate advanced statistics for a single player from MLB Stats, Baseball Savant, and FanGraphs. Use Yahoo's browser pages separately for league scoring, ownership, roster, and lineup context. |
| analyze_players_statsA | Fetch MLB Stats, Baseball Savant, and FanGraphs analysis for up to 10 players. Use this after reading roster or free-agent names from the signed-in Yahoo browser. Within each player, mlbStats.columns names the aligned values in mlbStats.standard and the optional mlbStats.recent14d and mlbStats.recent30d arrays. |
| list_probable_startersA | List every probable starting pitcher across MLB for a date, with opponent, home/away, and game time. This tool uses MLB Stats only. Read Yahoo ownership and availability separately from the signed-in Yahoo browser. |
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 5 tools
The preference tools are clearly distinguished (read vs write), and list_probable_starters is distinct. However, analyze_player_stats and analyze_players_stats overlap in function, differing only in player count, which could confuse an agent. Descriptions help, but the boundary is not as crisp as it could be.
Naming mixes a 'fantasy_' prefix for local preferences with bare action verbs for the stats tools, and the two analyze tools have inconsistent singular/plural forms. All names are snake_case and readable, but there is no unified pattern across the set.
With 5 tools, the server is well-scoped for its niche purpose of fetching advanced stats and managing local preferences. Each tool serves a clear role, and the count feels neither thin nor bloated.
The server covers single-player and batch stats analysis plus probable starters, which aligns with its stated external-data focus. Minor gaps exist, such as no head-to-head player comparison or expanded roster operations, but these fall outside its apparent design.