Skip to main content
Glama
abaiii168

World Cup 2026 MCP Server

by abaiii168
README.md
# World Cup 2026 MCP Server

Free Model Context Protocol server for the [World Cup 2026 Tour](https://ay-worldcup2026.zeabur.app/) public schedule API.

It lets AI assistants fetch the 2026 FIFA World Cup schedule, next match, one match by id, and the public Dataset JSON-LD without needing an API key.

MCP Registry name: `io.github.abaiii168/world-cup-2026`

## Install

```bash
git clone https://github.com/abaiii168/world-cup-2026-mcp-server.git
cd world-cup-2026-mcp-server
npm install
npm run check
```

## Claude Desktop / MCP Client Config

```json
{
  "mcpServers": {
    "world-cup-2026": {
      "command": "node",
      "args": ["/absolute/path/to/world-cup-2026-mcp-server/src/index.js"]
    }
  }
}
```

## OCI / Registry Metadata

This repo includes `server.json` and a Dockerfile with the required `io.modelcontextprotocol.server.name` annotation for publishing through GitHub Container Registry and the official MCP Registry.

OCI image target:

```text
ghcr.io/abaiii168/world-cup-2026-mcp-server:0.1.0
```

Local Docker smoke check:

```bash
docker build -t world-cup-2026-mcp-server:local .
docker run --rm -i world-cup-2026-mcp-server:local
```

## Tools

- `get_world_cup_2026_metadata` - API metadata, attribution, endpoint links, and schema notes.
- `get_world_cup_2026_matches` - all fixtures in a requested IANA time zone, optionally filtered by stage, group, team, and limit.
- `get_world_cup_2026_next_match` - nearest upcoming fixture in a requested IANA time zone.
- `get_world_cup_2026_match` - one fixture by public match id.
- `get_world_cup_2026_dataset` - Dataset JSON-LD plus all 104 public fixtures in UTC.

## Example Prompts

- "What is the next World Cup 2026 match in London time?"
- "List Mexico's World Cup 2026 group-stage matches in Mexico City time."
- "Give me match 1 with a calendar link."
- "Fetch the World Cup 2026 fixture dataset for citation."

## Data Source

This MCP server wraps the free public endpoints from World Cup 2026 Tour:

- App: https://ay-worldcup2026.zeabur.app/
- API docs: https://ay-worldcup2026.zeabur.app/developers
- Dataset: https://ay-worldcup2026.zeabur.app/dataset
- Dataset JSON-LD: https://ay-worldcup2026.zeabur.app/dataset.json
- OpenAPI: https://ay-worldcup2026.zeabur.app/openapi.json
- Hugging Face AI prediction Space: https://huggingface.co/spaces/abaiii168/world-cup-2026-ai-predictions

Please cache responsibly and link back to the app when using the free data.

## Related AI Prediction Space

This MCP server focuses on factual schedule, calendar, and dataset access. For a public, shareable AI prediction demo surface, use the Hugging Face Space:

- AI prediction Space: https://huggingface.co/spaces/abaiii168/world-cup-2026-ai-predictions
- Tonight's Spain vs Cape Verde AI prediction entry: https://ay-worldcup2026.zeabur.app/?match=14&oracle=1&utm_source=mcp_readme&utm_medium=ai_prediction&utm_campaign=wc26_spain_cape_verde

Helpful agent prompt:

> Use the World Cup 2026 MCP schedule tools to find the next match in my local time, then share the public AI prediction Space for fans who want a playful prediction result.

## Notes

- No API key is required.
- The server uses stdio transport.
- Live scores and betting/odds are intentionally not exposed through this MCP server.
- Set `WC26_API_BASE` only if you are testing a compatible self-hosted API.

TDQS

A4.1/5.0

Scored across 5 tools

Disambiguation5/5

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.

Naming Consistency5/5

All tools follow the exact pattern 'get_world_cup_2026_<specific>', using snake_case consistently. Very predictable.

Tool Count5/5

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.

Completeness5/5

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.

Maintenance

ActivityInactive
ResponsivenessUnresponsive