Developer documentation
TeamUp is an AI assistant that organizes amateur sports games inside a team's group chat. Everything the assistant can do is also reachable programmatically — this section documents the surfaces you can build on.
Five minutes from adding the bot to a full game — one real conversation: sign-ups, teams, score and dues. Also available in Russian.
The primary public API: a Model Context Protocol server with 58 tools — the same ones the in-chat assistant uses. OAuth 2.1 with dynamic client registration; works out of the box with Claude, Cursor and any MCP-compatible client.
The contract behind the web and iOS apps: 46 queries, 69 mutations and live subscriptions. The full SDL schema is published as a downloadable file.
Live CSV feeds for Google Sheets and Excel: events, attendance, player stats, and optionally dues and the cash ledger — one revocable link per group, made for =IMPORTDATA.
Which one do I want?
Building an AI agent or automation? Use MCP. It is the only surface with self-service authorization: any client can register, request access and call tools on behalf of a TeamUp user.
Just need the data in a spreadsheet? Use the CSV export feeds— no code at all, one formula per sheet.
Curious how the apps talk to the server? The GraphQL schema is the published contract. Note that its authentication is first-party (Telegram, VK and Apple sign-in) — there is no self-service client registration for GraphQL yet.
For AI crawlers
A machine-readable overview of the product and these APIs lives at /llms.txt. These docs are English-only; the product itself speaks 12 languages.