DiscGolfAPI

What DiscGolfAPI MCP server does

The DiscGolfAPI MCP server exposes disc golf course data through a remote MCP endpoint at https://io.discgolfapi.com/mcp. It is intended for applications that need structured access to course locations and related course information through Model Context Protocol.

Course discovery can use descriptive filters such as name, city, country, region, hole count, and course features. Location-based discovery uses a latitude and longitude pair with a radius measured in kilometers. When a specific course is already known, the API can return its details using either the course's unique ID or its alias.

How it works

An MCP-compatible client connects to the remote endpoint and invokes one of the exposed tools. The DiscGolfAPI MCP server passes the requested search or lookup to DiscGolfAPI services and returns the resulting course data to the client.

The available operations cover two discovery patterns. Attribute-based search helps narrow results using course metadata, while proximity search finds courses around supplied coordinates. A separate detail operation handles direct retrieval, and an update operation reports recently added or modified courses along with the change type and timestamp.

It also does not specify authentication or client-specific configuration requirements.

Tools and capabilities

The DiscGolfAPI MCP server exposes these tools:

• search_courses: Searches for courses using one or more supported criteria: name, city, country, region, hole count, or features.
• find_courses_near: Finds courses within a specified kilometer radius of given coordinates.
• get_course: Retrieves detailed information for a course identified by its unique ID or alias.
• get_recent_updates: Returns recently added or updated courses, including the change type and timestamps.

Together, these tools support both broad course discovery and direct access to a known course. They can also provide a way to identify changes in the course dataset, when recent additions or updates are relevant.

Applications that require a particular response field should verify it against the service documentation exposed through the endpoint.

Limitations and notes

Client compatibility is likewise not specified. Treat those details as unresolved until confirmed in the DiscGolfAPI documentation or by the endpoint itself.

The proximity tool requires coordinates and a radius in kilometers; the material does not define the coordinate order, accepted ranges, or default radius. The course detail tool accepts an ID or alias, but no identifier format is provided. Recent-update results include change types and timestamps, while the supported time range or ordering is not documented.