Commish MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YAHOO_CLIENT_ID | No | Yahoo client ID from an app registered at developer.yahoo.com/apps. | |
| YAHOO_REDIRECT_URI | No | Redirect URI for Yahoo OAuth2 callback. | http://localhost:8787/callback |
| YAHOO_CLIENT_SECRET | No | Yahoo client secret from an app registered at developer.yahoo.com/apps. |
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 |
|---|---|
| get_league_overviewA | Get a commissioner's overview of a fantasy league: league settings and current standings. |
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 1 tool
With only one tool available, there is no potential for confusion between tools. The purpose of get_league_overview is clear and unambiguous.
The single tool follows a clean verb_noun pattern, which is consistent with well-named MCP tools. There are no conflicting conventions.
A single tool is far too few for a server whose name implies commissioner functionality. While the tool itself is useful, one tool cannot reasonably cover the expected scope.
The server only provides a read-only league overview. Critical commissioner actions such as roster management, trade processing, waiver claims, or settings updates are entirely missing, leaving the surface severely incomplete.