app.turnale/turnale MCP Server

The app.turnale/turnale MCP server provides a hosted service (https://mcp.turnale.app) for running recreational racket-sport tournaments via an AI assistant. It supports creating fair tournament draws, producing schedules, and sharing a web page with live standings for players.

🛠️ Key Features

Run recreational racket-sport tournaments from chat with an AI assistant
Generate fair draws
Produce a schedule
Publish a shareable web page with live standings
Hosted service at https://mcp.turnale.app
Tool count: 30

🚀 Use Cases

Organize recreational tournaments through an assistant
Manage player participation by sharing “who’s playing”
Tennis, padel, pickleball, and badm are listed sports in the excerpt

⚡ Developer Benefits

Client integration manifests exist for the Claude Code plugin, the Gemini CLI extension, and the organiser skill
Uses Model Context Protocol (MCP) for tool access (per provided topics)

⚠️ Limitations

Server itself is a hosted service and “is not open source” (per excerpt)
Only the excerpted capabilities are documented; no further tool specifics are provided

Turnale

Run recreational racket-sport tournaments from chat.

This repository holds the client integration manifests for Turnale — the Claude Code plugin, the Gemini CLI extension, and the organiser skill. The server itself is a hosted service at https://mcp.turnale.app and is not open source.

What Turnale does

Turnale lets an organiser run an entire recreational tournament by talking to their AI assistant. Tell it who's playing and you get a fair draw, a schedule, and a shareable web page with live standings that players follow from their phones.

Tennis, padel, pickleball, badminton, squash and table tennis.

Formats clubs actually play

Americano and mexicano (rotating-partner doubles), round robin, groups + playoff, and knockout with an optional 3rd-place match — as singles or fixed pairs, with random or level-balanced pairing. The assistant explains the options with the round and time maths already done by the engine.

Last-minute chaos is one sentence

Dropouts, substitutions, partner swaps, late arrivals, court changes, and ending early with the standings frozen as the final result. Every change can be previewed before it lands and undone afterwards.

Honest scores

Walkovers and retirements are recorded as exactly that, and the games actually played still count towards the standings.

One link for players

The shareable page carries the order of play, live scores, standings and self-signup, with an optional cap and waitlist. Printable order-of-play and results PDFs cover the clubhouse noticeboard.

Connecting

Point your assistant at https://mcp.turnale.app and start straight away.

json

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

Creating a tournament returns an unguessable organiser key plus the shareable page link. The key is the only credential and is relayed in chat with a cannot-be-recovered warning; the page link on its own is view-only.

Per-platform connect steps for Claude, ChatGPT, Le Chat, Perplexity, Grok and the Gemini CLI are at turnale.app/docs.

Install as a Claude Code plugin

code

/plugin marketplace add turnale-app/turnale
/plugin install turnale

Install as a Gemini CLI extension

code

gemini extensions install https://github.com/turnale-app/turnale

Example prompts

Run a padel americano for 12 players on 3 courts, 2 hours.
Set up Thursday's tennis night — no player list yet, let people sign up via a link.
Jonas can't come, replace him with Emil from round 3.
Court 1: 9–7, Court 2: 11–5. Who plays whom next?
We have to stop early — freeze the standings and give me the final results.

Links

Website · Docs · Demo · Privacy · Terms

sport	string	required	Write sport names to the organiser in words — 'table tennis', never the enum spelling 'table_tennis'.
format	string	optional	Tournament format. round_robin: everyone plays everyone. groups_playoff: round-robin groups then a knockout. single_elimination: knockout with byes. americano/mexicano: rotating-partner doubles, points per round (mexicano pairs each round from standings). OMIT when the organiser hasn't clearly chosen — the call then returns a menu of explained options to show them instead of creating anything.
name	string	optional	Defaults to '<Sport> tournament 14 Aug 2026 (<location>)' — start date (or today) plus the location when known
discipline	string	optional	Ask the organiser — never infer it from the sport. Americano/mexicano are always doubles. Defaults to singles for the bracket formats when they truly have no preference.
players	array	optional
pairs	array	optional	Doubles: fixed pairs as [name, name] arrays. Omit to auto-pair.
courts	integer	optional	Default 2
court_names	array	optional
start_time	string	optional	ISO datetime with offset, e.g. 2026-08-01T18:00:00+03:00. Must be within 365 days from today.
match_duration_minutes	integer	optional
break_minutes	integer	optional	Changeover between matches/rounds, shown separately from play time (default 0)
page_results_entry	boolean	optional	Allow anyone with the page link to enter scores courtside. Default TRUE — recreational tournaments run on whoever finishes their match first, and an organiser who has to type every result is the bottleneck. Pass false if the organiser wants to be the only one recording scores; switchable either way at any time via update_settings or the toggle on the page.
language	string	optional	Language of the tournament page, PDFs and player emails. Default en; set et when the organiser works in Estonian.
seeding	string	optional	Default random
group_count	integer	optional
advance_per_group	integer	optional
third_place_match	boolean	optional	Single elimination; default true
points_per_match	integer	optional	Americano/mexicano; default 21
rounds	integer	optional	Americano/mexicano; default from player count
location	string	optional	Venue/location shown to players on the page, e.g. club name + city
house_rules	array	optional	Organiser's house rules, shown on the tournament page (e.g. 'Golden point at deuce')
signup_open	boolean	optional	Open self-signup: players add themselves on the shared page (name-only or signed in). Offer this when the organiser has no player list yet.
signup_cap	integer	optional	Signup limit; beyond it players join a waitlist
level_scale	string	optional	How to read the numbers in `level`. absolute (default): one shared scale, a 3 is a 3 whoever holds it. by_group: men and women were each rated within their own group, so the numbers are not directly comparable — ask the organiser which they did rather than guessing. ignore: the numbers are notes, never used for the draw.
level_offset	number	optional	by_group only: how much stronger an m is than an f carrying the SAME number, in the organiser's own level units. Default 1 — a starting point to adjust, not a fact. Used for balancing only; never shown on the page or in standings.
gender_balance	string	optional	Americano/mexicano: prefer matches where both teams have the same make-up (MM v MM, MW v MW, WW v WW). Default prefer_symmetric. A preference, not a rule — an uneven field cannot supply it, and the draw says so rather than distorting the rotation.
level_gap_cap	number	optional	Opt-in: the largest level gap the organiser wants between opponents, in their own level units. Soft — the draw prefers to respect it and reports when it cannot. Pass 0 to clear.

tournament_key	string	required	The tournament's organiser key (starts with tk_)
players	array	required
request_id	string	optional	Optional idempotency id — retrying a call with the same id never applies it twice

tournament_key	string	required	The tournament's organiser key (starts with tk_)
player_name	string	optional	Single update; or use `updates` for several
new_name	string	optional
gender	string	optional
level	number	optional	Any consistent numeric level/rating — used only for seeding and balancing
note	string	optional	Free note shown on the tournament page. Pass an empty string to clear it.
updates	array	optional	Bulk edit — e.g. levels for a whole roster in one call
request_id	string	optional	Optional idempotency id — retrying a call with the same id never applies it twice

tournament_key	string	required	The tournament's organiser key (starts with tk_)
player_name	string	optional
player_names	array	optional	Bulk removal — e.g. clearing mistaken placeholder names in one call
request_id	string	optional	Optional idempotency id — retrying a call with the same id never applies it twice

tournament_key	string	required	The tournament's organiser key (starts with tk_)
pairs	array	optional	Fixed pairs as [name, name] arrays
auto	string	optional
request_id	string	optional	Optional idempotency id — retrying a call with the same id never applies it twice

category	string	required
feedback	string	required	What the organiser wanted, summarised without any personal data (max 1000 characters — room for the problem, the workaround tried, and the suggested scope)
related_tool	string	optional	The tool this relates to, if any

players_estimate	integer	required
discipline	string	optional	Ask the organiser before offering formats; never infer it from the sport. 'unknown' = you asked and they don't mind, which shows both kinds. OMIT to get the question itself back.
courts	integer	optional	Default 2
total_minutes	integer	optional	The time budget, e.g. 120 for a two-hour evening
match_minutes	integer	optional
vibe	string	optional	Social: everyone mixes and plays a lot. Competitive: a bracket and a winner.
fixed_partners	boolean	optional	Doubles only: do pairs stay together all evening?

app.turnale/turnale MCP Server

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

ping

create_tournament

add_players

update_player

remove_player

set_pairs

update_settings

promote_player

generate_draw

get_briefing

list_players

list_matches

get_schedule

get_standings

get_results

get_audit_log

get_export

get_pdf_link

get_pdf

record_results

replace_player

withdraw_player

swap_partners

reschedule

end_tournament

undo_last_change

delete_tournament

record_feedback

suggest_format

get_player_template