Connect TeamUp to any AI agent

Our backend speaks the Model Context Protocol (MCP). Plug TeamUp into Claude Desktop, Cursor, your own custom agent, or any MCP-compatible client and they get the same tools, elicitation prompts, and live event log as the built-in Telegram/VK bot.

What an MCP client gets

Tools

~20 mutating + 9 read-only tools: createEvent, registerFor, splitTeams, finishEvent, getRegistrations, listMyEvents, and more. All annotated with destructiveHint / readOnlyHint.

Elicitation

Multi-choice prompts mid-tool-call (e.g. candidate disambiguation). Server pauses, client renders the picker, user picks, server resumes.

Resources

Pull-readable URIs: team-up://event/{id}/log, team-up://event/{id}/snapshot, team-up://chat/{id}/messages. Subscribe and receive notifications/resources/updated when state changes.

OAuth 2.1

PKCE S256, public clients, no shared secret. Dynamic client registration (RFC 7591). Most clients auto-discover the flow from the resource metadata.

Quick start: Claude Desktop

1. Open Claude Desktop → Settings → Developer.

2. Add a new MCP server with this URL:

{
  "mcpServers": {
    "team-up": {
      "url": ""
    }
  }
}

3. Claude opens an authorization page — sign in here, approve the request, and you're connected.

Custom client / scripts

Discover everything via the standard well-known endpoints:

Protected resource metadata (RFC 9728):
Authorization server metadata (RFC 8414):
MCP server endpoint (Streamable HTTP):

Personal access token

Need a token for a one-off curl / script / non-MCP client? Generate one here. The token is a regular OAuth 2.1 access_token tied to your account, valid for 1 hour. Refresh tokens are issued alongside.