Time-zone conversion is where World Cup schedules usually go wrong, and here it is a parameter on every query rather than arithmetic done afterwards. The JSON-LD dataset alongside the fixtures makes it usable as a citable source, not only a lookup.
A Node.js MCP server wrapping the free public schedule API of World Cup 2026 Tour, registered as io.github.abaiii168/world-cup-2026.
- All fixtures in a requested IANA time zone, filterable by stage, group, team and count
- The nearest upcoming fixture, also resolved to the time zone you name
- A single fixture by its public match id
- The Dataset JSON-LD together with all 104 public fixtures in UTC, for citation or bulk use
- API metadata: attribution, endpoint links and schema notes
- A Dockerfile and server.json carrying the MCP registry annotation, for publishing through a container registry
Nothing — no API key. Node with npm for the local install, or the published Docker image. The maintainer asks that responses be cached responsibly and that the app be linked when the free data is used.
One command — docker run --rm -i world-cup-2026-mcp-server:local
