FPL Strategy MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FPL_MCP_BEARER_TOKEN | No | A bearer token used to protect the HTTP/streamable transport when running in remote mode (e.g., `fpl-strategy-mcp --transport streamable-http`). If set, the health endpoint and MCP endpoint require this token. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fpl_recommend_movesB | Return legal FPL transfer moves for the current gameweek using the frozen champion strategy by default. Give a full 15-player current squad, buyable players, point-in-time signals or enable auto_official_signals, bank/free transfers, unused chips, and optional mini-league standings context. The default champion ranks hold and legal free transfers; explicit hybrid challengers can rank Wildcard, Free Hit, Bench Boost, and Triple Captain when model-backed. |
| fpl_strategy_infoA | Return the selected strategy, benchmark status, research sources, and known limitations. |
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 2 tools
The two tools are clearly distinct: one generates transfer recommendations, the other provides meta-information about the strategy itself. There is no overlap in purpose or output.
Both tools share the 'fpl_' prefix and use readable noun/verb combinations. 'fpl_recommend_moves' follows verb_noun while 'fpl_strategy_info' is noun_noun, a minor deviation from a strict pattern.
Two tools is a thin surface for a strategy server, but it covers the core need of getting recommendations and understanding the strategy. It feels slightly sparse but not unreasonable.
The domain is FPL strategy recommendations, and the pair covers the main action (recommend moves) and necessary context (strategy info). A tool to explicitly set or switch strategies is missing, but the primary workflow is supported.