Turnale

Last 30 days

Uptime

100%

Response time

268 ms typical, 268 ms slowest 5%

Last check

4 h ago

Next check

in 2 h

How to call it

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "turnale": {
      "type": "http",
      "url": "https://mcp.turnale.app"
    }
  }
}

30 tools

• ping

  Health check. Returns a static confirmation that the Turnale MCP server is reachable.

• create_tournament

  Create a new tournament. Keep setup SHORT: ask the organiser only for sport, players, court count and start time — sensible defaults cover everything else. FORMAT: never ask an open 'which format?' question. If the organiser clearly named one, pass it; otherwise omit format — the

• add_players

  Add players to the roster in bulk (parse pasted lists or spreadsheets yourself and send structured entries — never invent placeholder names; use signup mode when names aren't known yet). Duplicate names are rejected for disambiguation. If an unlocked draw exists it is regenerated

• update_player

  Rename a player or set their gender/level/note. Updates MANY in one call: pass `updates` with one object per player and never loop one-by-one — setting levels for a whole roster used to be one call per player, which on a phone meant approving each one and left the roster half-upd

• remove_player

  Remove one or MANY players before any result is recorded (afterwards use withdraw_player or replace_player) — pass player_names to clear several in one call, never loop one-by-one. Regenerates an existing unlocked draw.

• set_pairs

  Fix the doubles pairs: pass explicit pairs by name, or auto-pair (random or level-balanced). Only before results exist. Regenerates an existing unlocked draw.

• update_settings

  Change the tournament name, start time, match duration, break/changeover minutes, courts (count or names), house rules, or courtside score entry from the page. Court changes recompute the remaining schedule; played matches never move.

• promote_player

  Move a waitlisted player onto the active roster when a spot opens (signed-in players are notified by email). The cap can be raised with update_settings.

• generate_draw

  Generate (or regenerate) the draw and schedule. This IS the start action: the first draw moves the tournament from setup to active and closes self-signup — when the organiser says "start the tournament", call this. The result includes rounds_text — SHOW it to the organiser as-is,

• get_briefing

  Compact full state of the tournament — settings, roster, progress, next matches, standings, page link. Call this first when resuming work in a new conversation with just the key.

• list_players

  Full roster with status, level, and doubles partner.

• list_matches

  Matches with sides, scores, courts and times. Filter by state or round; paginate with after_match_number for large tournaments.

• get_schedule

  Upcoming matches in playing order with courts and estimated times.

• get_standings

  Current standings per group/structure, tiebreak-ordered (wins → head-to-head → set diff → game diff; americano: total points).

• get_results

  Final placements (or placements-so-far for a tournament that ended early).

• get_audit_log

  Chronological record of every change (newest first) — the answer to "who changed that?". Paginate with before_id. Ids are global across all tournaments, so gaps between ids are normal.

• get_export

  Full structured export of the tournament document (players, draws, results) — for the organiser's own records or data portability.

• get_pdf_link

  Download links for the printable PDF. pdf_url is the merged tournament document (match sheet with write-in score boxes, player sheet, standings/results when they exist) — hand this to the organiser. results_pdf_url and plan_pdf_url are deprecated pre-merge variants kept for compa

• get_pdf

  The printable PDF itself, returned as a base64 embedded resource — use this when the organiser wants the file handed to them and your client cannot fetch URLs. Default "sheet": the merged tournament document (match sheet with write-in score boxes, player sheet, standings/results

• record_results

  Record one or many results. Score is conversational text: "6-4 3-6 10-7" (sets) or "16-8" (americano points). Outcomes: completed (default), walkover, retired (partial score allowed), cancelled, reinstate — reinstate CLEARS a recorded result and returns the match to scheduled (th

• replace_player

  A substitute takes over a player's spot. During play: slot takeover — completed results stay, the change is shown ("Anna, for Kristjan from R3"). Before the first result: choose mode slot_swap (default) or regenerate (re-pair and redraw using levels). Unknown substitute names are

• withdraw_player

  Withdraw a player (or their pair) mid-tournament. Remaining matches become walkovers for the opponents; americano regenerates its future rounds instead. Preview first, confirm to apply.

• swap_partners

  Exchange two players' places. Fixed-pair doubles: swaps partners between two pairs permanently (name one player from each pair). Americano/mexicano: pass `round` to swap two players' places in ONE unplayed round — the courtside patch for a late arrival, an injury, or two friends

• reschedule

  Shift the start time, add a delay, or move one match to a specific court/slot. Played matches never move.

• end_tournament

  Finish the tournament. If matches are still pending it ends early and current standings freeze as the final results. Preview first, confirm to apply.

• undo_last_change

  Roll the tournament back. Without to_change_id: restore exactly how it was before the most recent change (tool call or courtside page entry). With to_change_id (an id from get_audit_log): restore to just before that change — it and every later change are discarded in one step, so

• delete_tournament

  Soft-delete the whole tournament (recoverable by support for 7 days, then gone). Preview first; confirm: true to apply.

• record_feedback

  Record a request for something Turnale does not support yet (a format, scoring variant, or feature), so it can be considered for the roadmap. Call this only when the organiser asked for something unsupported AND agreed to have it noted. Describe the missing capability in general

• suggest_format

  Recommend tournament formats in plain language, with the round/time math done by the engine. Call this FIRST when the organiser has not named a format, names one hesitantly, or comes from a background where americano/mexicano need explaining — then relay the `menu` text as-is ins

• get_player_template

  A blank Excel workbook the organiser fills in and hands back: Name, Level, Gender, Comments, one player per row, with a sheet explaining each column. Offer it when the organiser has no list ready, asks how to send their players, or would rather work in a spreadsheet than paste na

Security scan

• No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks