fpl-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FPL_COOKIE | No | Full Cookie header from a logged-in FPL request. Needed for authenticated reads/writes. | |
| FPL_ENTRY_ID | No | Your team ID (the number in fantasy.premierleague.com/entry/<ID>/). Needed for my_squad and make_transfer. |
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 |
|---|---|
| current_gameweekA | Return the current (or next upcoming) FPL gameweek and its deadline. |
| recommend_playersA | Rank available players by a blend of form, value (points per £m), and upcoming fixture difficulty. |
| my_squadA | Show your current squad (requires FPL_ENTRY_ID and FPL_COOKIE). |
| make_transferA | Transfer one player out and another in. Previews (dry run) unless confirm=true. |
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 4 tools
Each tool serves a distinct purpose: gameweek info, player recommendations, squad viewing, and transfers. No overlap.
All names use snake_case, but verb placement varies: 'current_gameweek' uses adjective, others use verb_noun. Mostly consistent.
4 tools cover basic FPL operations but feel minimal. Could expand with chip management or league features.
Core CRUD-like operations present: read gameweek, read squad, create transfer. Missing updates (e.g., squad order) and chip actions.