mocop
Browse · Docs · Guide · Analyze

POFA Tournaments

MCP server by POFA · mcp

POFA runs small tennis & pickleball tournaments. Player side (no credentials): search_tournaments to discover events, get_tournament for one event's details, get_schedule for match courts/times, get_bracket for the full draw with every match's state, get_roster for the player list, register_player to sign a player up — two-step: summary first, commit with confirm=true only after the user approves. Organizer side: create_tournament starts a new event and returns a manage_code, the per-tournament write credential required by import_players, generate_bracket, schedule_matches, report_result, screen_show, screen_clear and delete_tournament — run them in that order and keep the code. generate_bracket, schedule_matches and delete_tournament are preview-first: the first call writes nothing; show the preview to the user, then commit with the returned preview_id. Before undoing a result, call report_result with undo_preview=true to see what would be cleared; get_activity_log (manage_code) show…

Endpoint: https://pofa.app/mcp/

Verification: observed. Source: crawl.

Capabilities (19)

  • search_tournaments
  • get_tournament
  • get_schedule
  • get_bracket
  • get_roster
  • register_player
  • create_tournament
  • import_players
  • generate_bracket
  • schedule_matches
  • report_result
  • screen_show
  • screen_clear
  • get_screen
  • get_activity_log
  • delete_tournament
  • get_event_context
  • open_tournament_console
About · Contact · Privacy