mcpbeat

PGA Golf MCP Server

com.pga/pga-golf
answering

PGA Golf is answering right now. Last checked 3 min ago. It exposes 3 tools.

PGA's official MCP Server for all things golf-related. Find a coach, play golf, improve your game.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
451 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add pga-golf --transport http https://mcp.pga.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "pga-golf": {
      "url": "https://mcp.pga.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.pga-golf]
url = "https://mcp.pga.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "pga-golf": {
      "url": "https://mcp.pga.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "pga-golf": {
      "url": "https://mcp.pga.com/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

golf
get_golf_coach_availability
Retrieve offering details and available lesson times for one specific coach. Use this when the user asks for schedule, openings, or available times for a known coach. If the user has not selected a coach yet, call `search_golf_coaches` first. Coach `slug` and offering `id` values are internal identifiers and must never be shown or mentioned to the user.
search_golf_coaches
Search for qualified PGA golf coaches listed on pga.com/coach in the specified location (required). Use this tool when the user asks to find, browse, or compare coaches in a location. If the user asks for availability for a specific coach, use `get_golf_coach_availability` instead. Internal record identifiers (for example coach `slug` and offering `id`) are for tool calls only and must never be shown or mentioned to the user. - Search results include the coach's profile information, offerings, and pricing. - Results are ordered by proximity to the search location, so list them to the user in this order. - Results are paginated, so use the pagination cursor provided at the end of the response to retrieve the next page of results.
book
book_golf_lesson
Request to book a golf lesson for a specific coach's offering. - `offeringId` is an internal identifier; never show or mention it to the user. - A continuation URL will be returned that you can direct the user to after calling this tool. - If the offering was booked automatically (e.g., free lesson or no prepayment required), the confirmation code will also be included.

Endpoints

URLTransportStateLatencyChecked
https://mcp.pga.com/mcp streamable-http answering 438 ms 3 min ago

PGA Golf — questions

Answers built from our own checks of this server.

What can PGA Golf do?
It exposes 3 tools, read directly from the server on our last check. Among them: book_golf_lesson, get_golf_coach_availability, search_golf_coaches. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is PGA Golf working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 451 ms. The bar chart above shows every period we have measured.
How do I connect PGA Golf?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does PGA Golf need an API key?
No. PGA Golf completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is PGA Golf?
It answers our handshake in 451 ms on average, which is faster than 27% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.