Copa do Mundo 2026
Schedules and results for the 2026 FIFA World Cup in natural language: today's matches, kickoff time
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeRead-only
What it can do
What data it sees
Do you need an account
No: the server works without sign-in
Schedules and results for the 2026 FIFA World Cup in natural language: today's matches, kickoff time
Server tool list (14)
Raw names from tools/list. Only developers need these.
| worldcup_matches | Jogos da Copa do Mundo 2026 com placar e horário. Filtre por data (YYYY-MM-DD), seleção, grupo, fase ou status. Sem filtro, retorna os jogos de hoje. Use para 'que horas joga o Brasil', 'jogos de hoje', 'qual foi o placar de X'. |
| worldcup_schedule | Calendário do torneio agrupado por data. Use para ver a tabela de jogos de um dia, de uma fase ou da Copa inteira. |
| worldcup_results | Resultados (placares finais) dos jogos já encerrados. Filtre por data, seleção ou grupo. Use para 'resultados de ontem', 'como o Brasil se saiu'. |
| worldcup_groups | Composição dos grupos (12 grupos de 4 seleções) com as equipes e os jogos de cada grupo. Use para 'quem está no grupo do Brasil'. |
| worldcup_standings | Classificação (tabela) dos grupos: pontos, jogos, vitórias, empates, derrotas, saldo de gols. Use para 'como está a tabela do grupo C'. |
| worldcup_bracket | Chaveamento do mata-mata (16 avos até a final) com os confrontos e os classificados conhecidos. Use para 'como está o chaveamento'. |
| worldcup_teams | Seleções participantes (48 no total) com ranking FIFA e confederação. Passe `team` para o perfil de uma seleção específica. |
| worldcup_venues | Estádios-sede (16 nos EUA, México e Canadá): cidade, capacidade e os jogos de cada sede. Passe `city` ou `venue` para filtrar. |
| show_version | Show the current MCP platform and adapter versions. |
| report_bug | Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction. |
| connect | Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs. |
| toolkit_info | Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes. |
| marketplace | The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login. |
| authenticate | MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link. |