Model Context Protocol

The API exposes a native MCP endpoint:

https://api.eae.golf/mcp

MCP uses the same Bearer API key, plan, trial catalogue, data-access policy and rate limits as the REST API.

Authentication

Send the API key in the Authorization header:

Authorization: Bearer YOUR_API_KEY

Use the MCP endpoint only from environments where the credential can be kept secret. Do not expose a production API key in frontend JavaScript.

Available tools

The server currently exposes:

Tool	Purpose
search_golf_clubs	Search by place, coordinates, access rules, green fee, holes and other supported filters. Each result includes id, the stable club UUID.
get_golf_club	Retrieve one normalized golf club. Pass the search result UUID as identifier.
get_golf_club_context	Retrieve compact, language-neutral context. Pass the search result UUID as identifier.

Tool schemas are discoverable through MCP tools/list. Clients should use the discovered schema rather than hard-coding tool arguments.

Identify a club for detail tools

Use the stable id UUID returned by search_golf_clubs for subsequent detail operations:

search_golf_clubs → result.id → get_golf_club({ "identifier": result.id })

get_golf_club and get_golf_club_context accept either identifier or the legacy slug argument. identifier is preferred; it accepts the UUID from search (and also accepts a slug). slug remains available only for backwards-compatible callers. Do not send properties outside this tool schema.

Available prompts

MCP prompts/list exposes these prompt definitions:

• club-summary
• visitor-briefing
• club-comparison
• club-recommendation
• natural-language-search

Prompt definitions remain model-independent and follow the same rules for grounded answers and unknown values as the AI Toolkit.

Verify the connection

A raw MCP request can be used to verify tool discovery:

curl 'https://api.eae.golf/mcp' \
  --request POST \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --header 'Accept: application/json, text/event-stream' \
  --data '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list"
  }'

A successful response contains the registered tools.

Call a tool

For example, search for clubs near Berlin that allow independent players:

curl 'https://api.eae.golf/mcp' \
  --request POST \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --header 'Accept: application/json, text/event-stream' \
  --data '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/call",
    "params": {
      "name": "search_golf_clubs",
      "arguments": {
        "near": "Berlin",
        "independent_players": true
      }
    }
  }'

Tool results include MCP text content and structured content. Structured content preserves the normalized API response for clients that consume typed results directly.

Retrieve club details

After selecting a search result, call get_golf_club with its UUID:

{
  "name": "get_golf_club",
  "arguments": {
    "identifier": "86fa999f-d341-4d77-81fa-7810e3d46568"
  }
}

For existing callers, this legacy slug form remains supported:

{
  "name": "get_golf_club",
  "arguments": {
    "slug": "golf-gut-glinde"
  }
}

Access rules

MCP does not bypass API entitlements. The authenticated client determines:

• Fairway or Tour data access
• trial or active catalogue
• rate limits
• access status

The same request therefore follows the same data policy whether it reaches the underlying functionality through REST or MCP.

MCP or AI Toolkit?

Use MCP when the AI client supports remote MCP and can securely send the Bearer credential. Tool and prompt discovery are handled through the protocol.

Use the AI Toolkit REST endpoints when the application controls its own model tool-calling loop or needs the definitions independently of MCP.

Both interfaces use the same normalized golf data and domain semantics.