Provides tools for accessing 2026 FIFA World Cup match data, including today's matches, teams, scores, and venues.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@World Cup 2026 show me today's World Cup 2026 matches"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server that exposes 2026 FIFA World Cup data as tools for clients such as Claude Desktop.
get_today_matches — returns the matches scheduled for today's date (home/away teams, kickoff time, venue, round, group, score and goals, when available).
Related MCP server: mcp-football
Python >= 3.10
uv syncuv run mcp dev server.pyuv run mcp install server.py --name "World Cup 2026"This adds the server under mcpServers in claude_desktop_config.json. Restart Claude Desktop for the tool to appear.
uv run server.pyMatch data lives in data/worldcup.json, with the following structure per match:
Field | Description |
| Competition stage (e.g. |
| Match number |
| Date in |
| Kickoff time (with UTC offset) |
| Home / away team |
| Group stage group |
| Match venue |
| Score ( |
| List of goals (scorer name and minute) for each team |
.
├── server.py # Defines the MCP server and registers tools
├── providers/
│ └── worldcup.py # Reads and processes data/worldcup.json
└── data/
└── worldcup.json # Match dataReturns a list of matches scheduled for today in the World Cup 2026.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, but the description discloses the read-only nature (returns a list) and temporal scope. However, it lacks details like timezone handling or data freshness, preventing a higher score.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence with no wasted words, front-loading the action and resource.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter read tool with simple output, the description adequately covers the tool's function. No output schema exists, but the description suffices.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist, so baseline 4 applies. The description adds no param info, which is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb 'Returns' and resource 'matches scheduled for today in the World Cup 2026', clearly stating the tool's function. With no sibling tools, differentiation is unnecessary.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage context (when you need today's matches) without explicit when-not or alternatives, which is acceptable given the lack of siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v0.1.0get_today_matchesScored across 1 tool
Only one tool exists, so there is no possibility of ambiguity between tools.
With a single tool, naming consistency is not applicable; the name is clear and follows a standard verb_noun pattern.
A World Cup 2026 server should have many more tools (e.g., for standings, teams, players, history) to cover the domain; a single tool is extremely inadequate.
The server only provides today's matches, leaving out critical functionality such as viewing previous results, team details, or future schedules, making it severely incomplete.
Schedules and results for the 2026 FIFA World Cup in natural language: today's matches, kickoff time
FIFA World Cup 2026 schedule MCP — 104 matches, 62 country teams, jerseys, venues, kickoff times.
Free World Cup 2026 prediction game with fixtures, picks, brackets, and leaderboards
Structured Japan sports schedules, fixtures, broadcasts, and live updates for AI agents.
