World Cup History MCP — by Zafronix. Every FIFA World Cup since 1930 as MCP tools. 23 tournaments, 1,168+ matches, 2,500+ players, 206 stadiums.
Connect Wc MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. World Cup History MCP — by Zafronix. Every FIFA World Cup since 1930 as MCP tools. 23 tournaments, 1,168+ matches, 2,500+ players, 206 stadiums. Squads, brackets, stadiums, trivia — searchable from Claude / Cursor / any MCP-aware agent. The wc mcp mcp server is what makes that connection.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
list_tournaments — Every WC 1930→2026 (year, host, champion)get_tournament — Full tournament: teams, brackets, awards, squadscompare_tournaments — Side-by-side stats for 2-6 yearssearch_players — Player name search across historyget_player_career — Every WC a player appeared inlist_teams — Every nation that ever played, optional confederation filterget_team — Cross-tournament summary for a countryget_team_roster — Full squad for one team in one yearlist_stadiums — Every WC venue with elevation + coordsget_stadium — Single venue by sluglist_matches — Filter by year / stage / dateget_match — Single match with score + attendance + refereeInstallation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Configuration is passed through the environment: WC_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Wc MCP's toolset — list_tournaments, get_tournament, compare_tournaments and 11 more — is a fair guide to whether it matches your workflow. It is maintained by zafronix; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Wc MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| list_tournaments | Every WC 1930→2026 (year, host, champion). |
| get_tournament | Full tournament: teams, brackets, awards, squads. |
| compare_tournaments | Side-by-side stats for 2-6 years. |
| search_players | Player name search across history. |
| get_player_career | Every WC a player appeared in. |
| list_teams | Every nation that ever played, optional confederation filter. |
| get_team | Cross-tournament summary for a country. |
| get_team_roster | Full squad for one team in one year. |
| list_stadiums | Every WC venue with elevation + coords. |
| get_stadium | Single venue by slug. |
| list_matches | Filter by year / stage / date. |
| get_match | Single match with score + attendance + referee. |
| get_trivia | Curated factual nuggets per year. |
| get_standings | Computed group tables with FIFA tiebreakers. |
{
"mcpServers": {
"wc": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/inspector"],
"env": {
"WC_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| WC_API_KEY | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.