World Cup 2026 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WC26_API_BASE | No | Base URL for a compatible self-hosted API (optional, for testing purposes only). Defaults to the public API. |
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_world_cup_2026_metadataA | Return metadata, attribution, endpoint links, and schema notes for the free World Cup 2026 Tour public API. |
| get_world_cup_2026_matchesA | Return World Cup 2026 fixtures in a requested IANA time zone, optionally filtered by stage, group, or team code/name. |
| get_world_cup_2026_next_matchA | Return the nearest upcoming World Cup 2026 fixture from the public schedule API in the requested IANA time zone. |
| get_world_cup_2026_matchA | Return one World Cup 2026 fixture by match id, including teams, venue, stage, kickoff, app link, share-card link, and calendar link. |
| get_world_cup_2026_datasetA | Return Dataset JSON-LD metadata and all 104 public fixtures in UTC for citation, indexing, or data-directory use. |
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
Each tool has a clearly distinct purpose: dataset returns full metadata and all fixtures, match by id, matches with filtering, metadata for API info, and next match. No overlap.
All tools follow the exact pattern 'get_world_cup_2026_<specific>', using snake_case consistently. Very predictable.
5 tools is appropriate for a focused World Cup 2026 fixture server. It covers retrieval of all data, single match, filtered list, metadata, and next match without being excessive.
The tool set covers all common retrieval needs for a fixture data source: getting all fixtures, by ID, filtered, next match, and metadata. No obvious gaps given the read-only domain.