Totem MCP server

Totem speaks the Model Context Protocol (MCP). AI agents (Claude, ChatGPT, your own LLM stack) can connect and call tools that create events, invite participants, advance games, and read game-type documentation.

Endpoint

https://dev-139.staging.gojad.co/mcp

JSON-RPC 2.0 over HTTPS. Bearer-token authenticated.

OAuth metadata (auto-discovery)

RFC 9728 + RFC 8414. Most MCP clients fetch these automatically once they receive a 401 from the endpoint above.

Connect Claude or ChatGPT

  1. Point your MCP client at the endpoint URL above.
  2. The client receives a 401 with a WWW-Authenticate header pointing at the protected-resource doc.
  3. It POSTs to https://dev-139.staging.gojad.co/mcp/oauth/register for Dynamic Client Registration (RFC 7591) and gets back a client_id / client_secret.
  4. It runs the Authorization Code + PKCE flow against the authorization server, presents the resulting access token on every JSON-RPC call, and starts invoking tools.

Available tools

Tool names exposed by tools/list (visibility filtered by the caller's role at runtime):

  • cancel_event
  • complete_game
  • create_event
  • create_participation
  • delete_event
  • get_event
  • get_game_guide
  • invite_participant
  • list_allowed_game_types
  • list_event_participants
  • list_upcoming_events
  • move_game_to_next_step
  • move_game_to_previous_step
  • send_invitations
  • support.list_recent_conversations
  • support.read_conversation
  • update_event

Game-type resources

Workflow documentation served by resources/list / resources/read (filtered by the caller's permissions):

  • totem://game-types/ice_breaker_game
  • totem://game-types/play_totem_live_game
  • totem://game-types/play_totem_game
  • totem://game-types/all_for_one_celebration_game
  • totem://game-types/all_for_one_welcome_game
  • totem://game-types/tb_live_two_totems_live_game

Server identity

  • Name: totem-ai-chatbot
  • Version: 1.0
  • Protocol version: 2024-11-05