Disc Golf MCP

What Disc Golf MCP MCP server does

Disc Golf MCP provides read-only access to disc golf information from the Professional Disc Golf Association (PDGA). Its stated coverage includes four data areas: players, events, courses, and season statistics. The service is intended for retrieving information, not creating, editing, or deleting PDGA records.

The Disc Golf MCP MCP server is a fit for applications that need disc golf data available through MCP-compatible tooling. For example, an agent could use the service as a source for questions about PDGA players, scheduled or recorded events, course information, or statistics associated with a season. The available description does not specify particular query parameters, response fields, geographic coverage, or historical limits.

How it works

The service presents PDGA disc golf data through the Model Context Protocol. MCP provides the connection format, while the source data is identified as PDGA information. The available material describes the service as read-only, so its supported purpose is data retrieval.

Its subject areas are broad enough to separate common disc golf lookup needs: player records, event data, course data, and season-based statistics. The source description does not provide tool names or example requests, so integrations should treat those details as unspecified until they are documented by the service.

Because the service is read-only, it should be evaluated as a reference or lookup endpoint. It is not documented as a system for managing PDGA data, submitting event changes, updating player profiles, or maintaining course records.

Tools and capabilities

The documented capabilities are:

• Read PDGA player data.
• Read PDGA event data.
• Read PDGA course data.
• Read statistics for disc golf seasons.
• Access the data through MCP.

The available description does not identify separate tool names, return schemas, filters, sorting options, pagination behavior, or authentication requirements. Those details should be confirmed from the service documentation before implementation.

Limitations and notes

Disc Golf MCP MCP server is documented as read-only. Any workflow that requires changing PDGA information is outside the stated scope. The provided material also does not confirm support for a specific MCP client, installation method, transport, environment variables, license, or authentication configuration.

No claims can be made here about live updates, coverage of particular countries or tours, historical depth, rate limits, reliability, or response formats. Developers choosing the service should verify those operational details directly with the source before depending on it in production.

The clearest use case is retrieval: give an MCP-compatible application access to PDGA players, events, courses, and seasonal statistics while keeping the integration non-mutating.