World Cup 2026 Tour

What World Cup 2026 Tour MCP server does

The World Cup 2026 Tour MCP server exposes factual schedule and dataset access for the 2026 FIFA World Cup. It wraps the public World Cup 2026 Tour API and makes its data available through MCP rather than requiring an assistant to call HTTP endpoints directly.

Available operations cover five areas:

• Read API metadata, attribution details, endpoint links, and schema notes.
• List fixtures in a selected IANA time zone.
• Find the nearest upcoming fixture in a selected time zone.
• Retrieve one public fixture by match ID.
• Return Dataset JSON-LD together with all 104 public fixtures in UTC.

The fixture-list operation can narrow results by tournament stage, group, team, and maximum result count. This makes the server suitable for questions about a particular team or phase as well as broad schedule queries.

How it works

An MCP client starts the process using stdio transport and invokes the exposed tools. The server requests schedule data from the free public World Cup 2026 Tour API, then returns structured results to the client. Time-zone-aware operations accept IANA time-zone names, allowing match times to be presented in locations such as London or Mexico City.

The data source includes a public application, API documentation, dataset endpoint, Dataset JSON-LD document, and OpenAPI description. The server is focused on factual fixtures, calendar-oriented schedule access, and dataset retrieval. It does not expose live scores or betting and odds information.

Setup and configuration

The repository setup flow is to clone the project, enter its directory, install its npm dependencies, and run the repository check command. A client configuration starts Node with the project’s src/index.js entry point. The README shows this configuration for Claude Desktop and notes that the path must be an absolute local path.

The World Cup 2026 Tour MCP server does not require an API key. An optional WC26_API_BASE environment variable can point to a compatible self-hosted API when testing; the material does not describe other configuration variables.

A Dockerfile and registry metadata are included. The repository also documents a local Docker build and interactive container smoke check, along with an OCI image target for the project.

Tools and capabilities

The five MCP tools are:

• get_world_cup_2026_metadata for API and schema information.
• get_world_cup_2026_matches for filtered fixtures in a requested IANA time zone.
• get_world_cup_2026_next_match for the closest upcoming fixture in a requested time zone.
• get_world_cup_2026_match for a single fixture selected by public match ID.
• get_world_cup_2026_dataset for Dataset JSON-LD and the complete public fixture set in UTC.

Example uses include finding the next match in local time, listing a team’s group-stage fixtures, and obtaining the fixture dataset for citation. The World Cup 2026 Tour MCP server can also expose API attribution and links when an agent needs source context.

Limitations and notes

No credentials are needed, but clients should cache responsibly and link back to the World Cup 2026 Tour application when using its free data. The server provides schedule and dataset information only; live scores, betting, and odds are intentionally outside its scope. The related Hugging Face AI prediction Space is a separate public demo and is not one of this server’s MCP tools.