Run small tennis & pickleball tournaments from your AI assistant: brackets, schedules, results.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Create a NEW tournament as an organizer — step 1 of the organizer flow: create_tournament → import_players → generate_bracket → schedule_matches → report_result. Takes effect immediately (no preview step). Returns the new tournament's id, share_url and manage_code. SAVE the manage_code and show it to the user: it is the write credential for every organizer tool on this tournament (import_players, generate_bracket, schedule_matches, report_result) and cannot be recovered later.
Tournament name as shown to players
Number of courts available
single_elimination (default), double_elimination, or round_robin
Venue / city text shown to players
Entry fee as display text, e.g. '$20' or 'Free'
First day of the event, YYYY-MM-DD
Public event description (max 500 chars)
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http pofa https://pofa.app/mcp/
Create a NEW tournament as an organizer — step 1 of the organizer flow: create_tournament → import_players → generate_bracket → schedule_matches → report_result. Takes effect immediately (no preview step). Returns the new tournament's id, share_url and manage_code. SAVE the manage_code and show it to the user: it is the write credential for every organizer tool on this tournament (import_players, generate_bracket, schedule_matches, report_result) and cannot be recovered later.
| Argument | Type | Description |
|---|---|---|
| name* | string | Tournament name as shown to players |
| courts | integer | Number of courts available |
| format | string | single_elimination (default), double_elimination, or round_robin |
| location | string | Venue / city text shown to players |
| entry_fee | string | Entry fee as display text, e.g. '$20' or 'Free' |
| start_date | string | First day of the event, YYYY-MM-DD |
| description | string | Public event description (max 500 chars) |
{
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "Tournament name as shown to players"
},
"courts": {
"type": "integer",
"description": "Number of courts available"
},
"format": {
"type": "string",
"default": "single_elimination",
"description": "single_elimination (default), double_elimination, or round_robin"
},
"location": {
"type": "string",
"description": "Venue / city text shown to players"
},
"entry_fee": {
"type": "string",
"description": "Entry fee as display text, e.g. '$20' or 'Free'"
},
"start_date": {
"type": "string",
"description": "First day of the event, YYYY-MM-DD"
},
"description": {
"type": "string",
"description": "Public event description (max 500 chars)"
}
}
}Generate the bracket for a tournament (organizer step 3, after the roster is in; needs manage_code). SINGLE-ELIMINATION ONLY in this version — tournaments of other formats return an error. PREVIEW FIRST: call without confirm_preview_id to get a preview_id and bracket preview — nothing is written. Show the preview to the user, then call again with {tournament_id, code, confirm_preview_id} to commit. The roster is the tournament's own player list (the same one the player page shows), paired by the same seeding the pages use; match ids are the pages' sequential labels M1, M2, ... A players list may be given to override the roster for the preview.
| Argument | Type | Description |
|---|---|---|
| code* | string | manage_code from create_tournament |
| format | string | Only 'single_elimination' is supported |
| players | array | Optional list of player names to preview with instead of the current roster |
| tournament_id* | string | Tournament id |
| confirm_preview_id | string | preview_id from the preview call — pass only to commit that exact preview |
{
"type": "object",
"required": [
"tournament_id",
"code"
],
"properties": {
"code": {
"type": "string",
"description": "manage_code from create_tournament"
},
"format": {
"type": "string",
"default": "single_elimination",
"description": "Only 'single_elimination' is supported"
},
"players": {
"type": "array",
"items": {
"type": "string"
},
"description": "Optional list of player names to preview with instead of the current roster"
},
"tournament_id": {
"type": "string",
"description": "Tournament id"
},
"confirm_preview_id": {
"type": "string",
"description": "preview_id from the preview call — pass only to commit that exact preview"
}
}
}Get a tournament's published schedule: match court/time assignments, dates and courts, plus the bracket size. Returns schedule: null with a note when the organizer has not published a schedule yet. Use for when/where questions about matches; use get_tournament for the event's own facts (format, fee, location). Read-only.
| Argument | Type | Description |
|---|---|---|
| id* | string | Tournament id, e.g. from search_tournaments |
{
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "Tournament id, e.g. from search_tournaments"
}
}
}Read what a tournament's venue call screen is currently showing: the on-screen match (court, both names, note) when one is up, plus a one-line summary of the console calling queue underneath it. Use to confirm a screen_show / screen_clear took effect. Read-only, no credentials needed.
| Argument | Type | Description |
|---|---|---|
| id* | string | Tournament id |
{
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "Tournament id"
}
}
}Get one tournament's full public details: format, dates, location, entry fee, description and its public share_url. Use after search_tournaments, or whenever you already have an event id, to answer questions about a specific event. For match courts and start times use get_schedule instead. Read-only.
| Argument | Type | Description |
|---|---|---|
| id* | string | Tournament id, e.g. from search_tournaments |
{
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "Tournament id, e.g. from search_tournaments"
}
}
}Bulk-add players to a tournament's roster (organizer step 2, right after create_tournament; needs that tournament's manage_code). Each player needs a name; email and phone are optional per player, but entries whose email duplicates an existing roster email are skipped. This roster is what generate_bracket seeds from. Returns how many were imported and which rows were skipped, and why.
| Argument | Type | Description |
|---|---|---|
| code* | string | manage_code from create_tournament |
| players* | array | Player objects to add: {name (required), email?, phone?}. Max 500 per call |
| tournament_id* | string | Tournament id |
{
"type": "object",
"required": [
"tournament_id",
"code",
"players"
],
"properties": {
"code": {
"type": "string",
"description": "manage_code from create_tournament"
},
"players": {
"type": "array",
"items": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"email": {
"type": "string"
},
"phone": {
"type": "string"
}
}
},
"description": "Player objects to add: {name (required), email?, phone?}. Max 500 per call"
},
"tournament_id": {
"type": "string",
"description": "Tournament id"
}
}
}Register one player into a tournament (player-side sign-up; no manage code needed). Duplicate-checked by email. TWO STEPS: first call WITHOUT confirm — it returns a summary and writes nothing; show that summary to the user, and only after they explicitly approve, call again with the same fields plus confirm=true to commit.
| Argument | Type | Description |
|---|---|---|
| name* | string | Player full name |
| email* | string | Player email — duplicates are detected by this address |
| phone | string | Optional contact phone |
| confirm | boolean | Set true only after user confirms the summary |
| division | string | Optional division / group label, if the event uses divisions |
| tournament_id* | string | Tournament id to register into |
{
"type": "object",
"required": [
"tournament_id",
"name",
"email"
],
"properties": {
"name": {
"type": "string",
"description": "Player full name"
},
"email": {
"type": "string",
"description": "Player email — duplicates are detected by this address"
},
"phone": {
"type": "string",
"description": "Optional contact phone"
},
"confirm": {
"type": "boolean",
"description": "Set true only after user confirms the summary"
},
"division": {
"type": "string",
"description": "Optional division / group label, if the event uses divisions"
},
"tournament_id": {
"type": "string",
"description": "Tournament id to register into"
}
}
}Report a match result (organizer step 5, on match day; needs manage_code). Recording a score advances the winner into the next round automatically and returns where they advanced to. Pass undo=true with the match_id to revert a result (cascades to auto-filled downstream slots). Overwriting an existing result is logged as a correction.
| Argument | Type | Description |
|---|---|---|
| code* | string | manage_code from create_tournament |
| undo | boolean | Set true (with match_id; winner/score not needed) to revert that match's result and its downstream effects |
| score | string | e.g. 6-4 6-3 |
| winner | string | exact player name as in the bracket (spelling must match) |
| match_id* | string | e.g. M1 (the player page's label for the match; legacy R1M1-style ids are also accepted) |
| score_sets | array | Optional structured per-set scores, written in parallel with the display string `score` (the display string keeps its own semantics). Each item is an object {p1: integer, p2: integer, tb?: [integer, integer]}, e.g. [{"p1": 6, "p2": 4}, {"p1": 7, "p2": 6, "tb": [7, 5]}], where tb is the optional tie-break points [p1, p2]. Stored in the match object and used to report results back to DUPR (required for rated events; the referee scoring UI blocks confirmation without it). Omitting it on an overwrite PRESERVES the existing score_sets (unlike `score`); pass an empty array [] to explicitly clear it, or a full array to replace it. |
Assign the bracket's matches to courts and start times (organizer step 4, after generate_bracket; needs manage_code). PREVIEW FIRST: call without confirm_preview_id — returns a preview_id plus per-match court/time assignments and conflict validation, and nothing is written. Show the preview to the user, then commit with {tournament_id, code, confirm_preview_id}.
| Argument | Type | Description |
|---|---|---|
| code* | string | manage_code from create_tournament |
| courts | integer | Number of courts to schedule across |
| start_time | string | First match start time, HH:MM, default 09:00 |
| match_minutes | integer | Minutes allotted per match |
| tournament_id* | string | Tournament id |
| confirm_preview_id | string | preview_id from the preview call — pass only to commit that exact preview |
{
"type": "object",
"required": [
"tournament_id",
"code"
],
"properties": {
"code": {
"type": "string",
"description": "manage_code from create_tournament"
},
"courts": {
"type": "integer",
"description": "Number of courts to schedule across"
},
"start_time": {
"type": "string",
"description": "First match start time, HH:MM, default 09:00"
},
"match_minutes": {
"type": "integer",
"default": 30,
"description": "Minutes allotted per match"
},
"tournament_id": {
"type": "string",
"description": "Tournament id"
},
"confirm_preview_id": {
"type": "string",
"description": "preview_id from the preview call — pass only to commit that exact preview"
}
}
}Take the current match off the venue call screen (needs manage_code). The screen falls back to the console calling queue board, or to the standby face when the queue is empty. Safe to call when nothing is on screen — it simply reports that. Does not touch the calling queue.
| Argument | Type | Description |
|---|---|---|
| code* | string | manage_code from create_tournament |
| tournament_id* | string | Tournament id |
{
"type": "object",
"required": [
"tournament_id",
"code"
],
"properties": {
"code": {
"type": "string",
"description": "manage_code from create_tournament"
},
"tournament_id": {
"type": "string",
"description": "Tournament id"
}
}
}Put ONE match on the venue call screen — the big display at the courts (the screen the organizer opens at the screen_url this tool returns). The screen immediately shows the court number huge with both player names, and keeps showing it until cleared. Use on match day when a specific match must be called out on the big screen. Needs the tournament's manage_code. This is an independent on-screen slot: it does NOT change the console calling queue — the queue board (or the standby face) comes back when you clear with screen_clear. Takes effect immediately, no preview step.
| Argument | Type | Description |
|---|---|---|
| code* | string | manage_code from create_tournament |
| note | string | Optional line shown with the match, e.g. 'Semifinal' or 'Final' |
| court* | string | Court label as shown, e.g. '3' or 'Center' |
| player_a* | string | First player / side name, exactly as it should appear on the big screen |
| player_b* | string | Second player / side name, exactly as it should appear on the big screen |
| tournament_id* | string | Tournament id |
{
"type": "object",
"required": [
"tournament_id",
"code",
"player_a",
"player_b",
"court"
],
"properties": {
"code": {
"type": "string",
"description": "manage_code from create_tournament"
},
"note": {
"type": "string",
"description": "Optional line shown with the match, e.g. 'Semifinal' or 'Final'"
},
"court": {
"type": "string",
"description": "Court label as shown, e.g. '3' or 'Center'"
},
"player_a": {
"type": "string",
"description": "First player / side name, exactly as it should appear on the big screen"
},
"player_b": {
"type": "string",
"description": "Second player / side name, exactly as it should appear on the big screen"
},
"tournament_id": {
"type": "string",
"description": "Tournament id"
}
}
}Find POFA tournaments (tennis & pickleball) by keyword, city, or start date. Returns each event's id, name and one-line summary. Start here whenever the user wants to discover, browse or pick an event; follow with get_tournament for one event's full details. Read-only, no credentials needed.
| Argument | Type | Description |
|---|---|---|
| city | string | City filter, matched against the event's location text |
| limit | integer | Max results to return, 1-25 |
| query | string | Keyword matched against the event name |
| date_from | string | Only events starting on/after this date (YYYY-MM-DD) |
{
"type": "object",
"properties": {
"city": {
"type": "string",
"description": "City filter, matched against the event's location text"
},
"limit": {
"type": "integer",
"default": 10,
"description": "Max results to return, 1-25"
},
"query": {
"type": "string",
"description": "Keyword matched against the event name"
},
"date_from": {
"type": "string",
"description": "Only events starting on/after this date (YYYY-MM-DD)"
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 8, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.
| tournament_id* | string | Tournament id |
{
"type": "object",
"required": [
"tournament_id",
"code",
"match_id"
],
"properties": {
"code": {
"type": "string",
"description": "manage_code from create_tournament"
},
"undo": {
"type": "boolean",
"description": "Set true (with match_id; winner/score not needed) to revert that match's result and its downstream effects"
},
"score": {
"type": "string",
"description": "e.g. 6-4 6-3"
},
"winner": {
"type": "string",
"description": "exact player name as in the bracket (spelling must match)"
},
"match_id": {
"type": "string",
"description": "e.g. M1 (the player page's label for the match; legacy R1M1-style ids are also accepted)"
},
"score_sets": {
"type": "array",
"items": {
"type": "object",
"required": [
"p1",
"p2"
],
"properties": {
"p1": {
"type": "integer",
"description": "points/games won by the player in slot p1 in this set"
},
"p2": {
"type": "integer",
"description": "points/games won by the player in slot p2 in this set"
},
"tb": {
"type": "array",
"items": {
"type": "integer"
},
"maxItems": 2,
"minItems": 2,
"description": "optional tie-break score [p1, p2], exactly two integers"
}
}
},
"description": "Optional structured per-set scores, written in parallel with the display string `score` (the display string keeps its own semantics). Each item is an object {p1: integer, p2: integer, tb?: [integer, integer]}, e.g. [{\"p1\": 6, \"p2\": 4}, {\"p1\": 7, \"p2\": 6, \"tb\": [7, 5]}], where tb is the optional tie-break points [p1, p2]. Stored in the match object and used to report results back to DUPR (required for rated events; the referee scoring UI blocks confirmation without it). Omitting it on an overwrite PRESERVES the existing score_sets (unlike `score`); pass an empty array [] to explicitly clear it, or a full array to replace it."
},
"tournament_id": {
"type": "string",
"description": "Tournament id"
}
}
}