POFA MCP

POFA MCP server enables AI assistants to manage tennis and pickleball tournaments directly. It supports searching public events, registering players, creating tournaments, importing rosters, generating brackets, scheduling matches, and reporting results. The server distinguishes between read-only access for anyone and write access for organizers using a management code.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Vendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-08Operated by POFA

MCP endpoint (Streamable HTTP)

https://pofa.app/mcp/

Vendor documentation

What its tools do

9 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (9)

search_tournaments
get_tournament
get_schedule
register_player
create_tournament
import_players
generate_bracket
schedule_matches
report_result

9 of 9 have a description · 0 of 9 declare behavior hints · 9 of 9 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 8, 2026, 2:17 PM UTC
Passed Official MCP Registry namespace is tied to pofa.app · Nov 8, 2026, 2:14 PM UTC
Passed Endpoint is on the registry namespace domain · Nov 8, 2026, 2:14 PM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Search for local tennis or pickleball tournaments by keyword or date
Create a new tournament and generate a management code for organizers
Import player lists and generate single-elimination brackets
Report match scores and automatically advance winners

Source and maintenance

Vendor evidenceRegistry 1.1.0

mcp-registry: app.pofa/pofa@1.1.0 Project website

Protocol and capabilities

Server: pofa-mcp 1.1.0
MCP protocol negotiated in check: 2024-11-05
Tools: 9 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

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, 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 and report_result — run them in that order and keep the code. generate_bracket and schedule_matches are preview-first: the first call writes nothing; show the preview to the user, then commit with the returned preview_id.

Tools

9 advertised

search_tournaments

Advertised by the server during the last successful anonymous check.

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.

search_tournaments input schema

{
  "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)"
    }
  }
}

get_tournament

Advertised by the server during the last successful anonymous check.

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.

get_tournament input schema

{
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Tournament id, e.g. from search_tournaments"
    }
  }
}

get_schedule

Advertised by the server during the last successful anonymous check.

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.

get_schedule input schema

{
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Tournament id, e.g. from search_tournaments"
    }
  }
}

register_player

Advertised by the server during the last successful anonymous check.

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.

register_player input schema

{
  "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"
    }
  }
}

create_tournament

Advertised by the server during the last successful anonymous check.

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.

create_tournament input schema

{
  "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)"
    }
  }
}

import_players

Advertised by the server during the last successful anonymous check.

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.

import_players input schema

{
  "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"
    }
  }
}

generate_bracket

Advertised by the server during the last successful anonymous check.

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.

generate_bracket input schema

{
  "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"
    }
  }
}

schedule_matches

Advertised by the server during the last successful anonymous check.

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}.

schedule_matches input schema

{
  "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"
    }
  }
}

report_result

Advertised by the server during the last successful anonymous check.

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.

report_result input schema

{
  "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"
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 368 ms
95th percentile latency: 368 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 8, 2026, 2:17 PM UTC · probe · passed · 368 ms · metadata changed · 9 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http pofa-mcp https://pofa.app/mcp/

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add pofa-mcp --url https://pofa.app/mcp/

Cursor

Merge this server into .cursor/mcp.json in your project, then enable pofa-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "pofa-mcp": {
      "url": "https://pofa.app/mcp/"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "pofa-mcp": {
      "type": "streamableHttp",
      "url": "https://pofa.app/mcp/",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start pofa-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "pofa-mcp": {
      "type": "http",
      "url": "https://pofa.app/mcp/"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http pofa-mcp https://pofa.app/mcp/

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.

Claude Desktop configuration

https://pofa.app/mcp/

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "pofa-mcp": {
      "serverUrl": "https://pofa.app/mcp/"
    }
  }
}

Let your agent find its tools

Find servers like POFA MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

Do you run POFA MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing