FantasyPros MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FANTASYPROS_API_KEY | Yes | Your FantasyPros API key (obtained by emailing FantasyPros) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_sport_newsC | Get news for a specific sport |
| get_playersC | Get player information for a specific sport |
| get_rankingsC | Get consensus rankings for a sport |
| get_projectionsC | Get player projections for a sport |
| get_all_newsC | Get all news from FantasyPros |
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
Most tools have distinct purposes targeting different data types (news, players, projections, rankings), but there is some overlap between get_all_news and get_sport_news that could cause confusion about which to use for sport-specific news. The descriptions help clarify, but the boundaries are not perfectly clear.
All tool names follow a consistent verb_noun pattern with 'get_' prefix and snake_case, making them predictable and readable. There are no deviations in naming conventions across the set.
Five tools is reasonable for a fantasy sports data server, covering core data retrieval needs. It might be slightly thin if advanced features like updates or filtering are expected, but it aligns well with a read-only scope.
The tool set provides good read-only coverage for fantasy sports data (news, players, projections, rankings), but there are notable gaps such as no update, delete, or create operations, and no filtering or search tools beyond basic gets. This limits agent workflows to retrieval only.