Docs · Developers

POFA MCP Server

Connect ChatGPT, Claude, or any MCP client straight to POFA: find tournaments, register players, and run a whole event from creation to the final. Live

MCP endpoint (remote · Streamable HTTP)

https://pofa.app/mcp/

This is not a demo page — the line has already carried a real run. On 2026-11-08 an AI ran a complete 8-player single-elimination test event ("Silicon Valley Test") through this MCP end-to-end: created the event, imported the roster, generated the bracket, and reported scores match by match to a decided champion — then verified the undo cascade step by step. 23 checks, all green. See that event's public page →

What this is

An MCP (Model Context Protocol) server. Any MCP-capable AI client connects to the URL above and can call POFA directly. Nothing to install.
One endpoint, two roles. Player side: discover events, read details and schedules, register — no credentials. Organizer side: create, roster, bracket, schedule, results — every write authorized by that tournament's manage code.
The same data as the web app. A score reported here shows up on the player page and the console immediately; seeding and match labels (M1, M2, …) match the pages exactly.

Running an event in six steps

Create

Creates the event and its manage code — hand the code to the organizer to keep

create_tournament

Roster

Bulk-adds the player list; duplicate emails are skipped

import_players

Bracket

Preview first for a human look; commits only on confirm

generate_bracket

Schedule

Assigns matches to courts and times; preview-first too

schedule_matches

Results

Winners advance automatically; mistakes undo with cascade

report_result

Big screen

On match day, put a match on its own court's screen — one screen and one link per court, never overwriting each other — until cleared

screen_show

Tools (12)

Tool	What it does	Who	Auth
`search_tournaments`	Find tournaments by keyword, city, or date — the discovery entry point	Players / anyone	None
`get_tournament`	One event's full public details: format, dates, location, entry fee, share link	Players / anyone	None
`get_schedule`	The published schedule: court and start time for every match	Players / anyone	None
`register_player`	Register a player. Two-step: returns a summary for the user to approve before anything is written	Players	None
`create_tournament`	Create a new tournament; returns the event id, share URL, and manage code	Organizers	Issues the code
`import_players`	Bulk-import a player roster (up to 500 per call)	Organizers	Manage code
`generate_bracket`	Generate the bracket (single elimination for now). Preview first; a preview writes nothing	Organizers	Manage code
`schedule_matches`	Place bracket matches on courts and times, with conflict validation; preview first	Organizers	Manage code
`report_result`	Record a score; the winner advances automatically. Supports undo and corrections	Organizers	Manage code
`screen_show`	Put one match on its own court's screen — both names, full screen, until cleared; each court shows its own match. Independent of the console calling queue	Organizers	Manage code
`screen_clear`	Take a match off the screen: with a court, only that court's screen; without one, every screen at once. The display falls back to the calling queue board (or the standby face)	Organizers	Manage code
`get_screen`	Read what every court's screen is showing, get all court screen links in one call, plus a summary of the calling queue	Organizers / anyone	None

Call screens: one screen per court

Every court has its own screen link: https://pofa.app/call/screen/?t=EVENT_ID&court=COURT. Four courts means four links — open one on each display and each shows its own match, independently.
All links in one call: when the event declares its court count, get_screen lists the link for every court (including idle ones) — no need to build links one by one.
The link without court is the global screen: it shows the most recently called match — right for venues with a single big display — and falls back to the console calling board, then the standby face.
An idle court's screen shows a standby face with its court number and the event name — never a black screen, never another court's match.

Connect from ChatGPT

Open ChatGPT, go to Settings → Connectors, and create a new custom connector.
Name it POFA, set the URL to https://pofa.app/mcp/, choose no authentication, and create it.
Enable the connector in a chat and just ask: "Find pickleball tournaments near me" or "Run an 8-player singles event for me".

Connect from Claude

Open Claude, go to Settings → Connectors, and choose Add custom connector.
Name it POFA, set the URL to https://pofa.app/mcp/, and save.
Any other remote-MCP client (Cursor and friends) takes the same URL.

Auth & safety

Reads need no credentials. Search, details, and schedules are as public as the event pages themselves.
Registration is two-step. The assistant first shows the user a summary of the sign-up; it is submitted only after the user explicitly approves — an AI never silently registers anyone.
Organizer writes run on the manage code. Each tournament gets one manage_code at creation, returned exactly once. It is the key to that single event: no valid code, no write — verified live, wrong codes write nothing. Treat it like a password; never post it publicly.
Bracket and schedule are preview-first. The first call produces a preview and writes nothing; only a second call carrying the preview id commits it, after a human has seen it.
Every write lands in the event's activity log — which channel, when, and what changed. See the permissions spec for the full model.

Current limits (stated plainly)

Bracket generation over MCP currently supports single elimination; double-elimination and round-robin events run on the POFA web app.
Scores can carry structured per-set data (score_sets), which rated-event reporting back to DUPR requires.
The live protocol version and tool list are authoritative at the endpoint itself: send initialize / tools/list and read what it returns.

POFA Docs · 中文版 · Related: Permissions · Data model