Koskamo

GolfCore MCP

An official MCP server providing public course data, including yardages, green maps, and wind models, for AI agents to assist golfers with course management and navigation.

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.

GolfCore MCP logo, by GolfCore LLCVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-07Operated by GolfCore LLC
MCP endpoint (Streamable HTTP)
https://mcp.golfcore.org/mcp
Vendor documentation

What its tools do

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

Read-only (3)

Can change data (6)

9 of 9 have a description · 9 of 9 declare behavior hints · 8 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 ·
  • Passed Official MCP Registry namespace is tied to golfcore.org ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Search for course data such as holes, pars, tees and coordinates
  • Provide yardages to the front, center and back of the green
  • Retrieve green maps with contour lines and fall-line arrows
  • Access live wind simulation data over the hole

Source and maintenance

Vendor evidenceRegistry 1.4.0
mcp-registry: org.golfcore/golfcore@1.4.0Project website

Protocol and capabilities

Server
GolfCore 1.4.0
MCP protocol negotiated in check
2025-11-25
Tools
9 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

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

GolfCore covers more than 30,000 golf courses in more than 180 countries and territories. On the course, when the golfer asks how far the flag is, call distance_to_flag; when they want advice on a shot, call ask_caddie with their question. Pass lat and lng only if your device gives you their GPS position, and never ask the golfer for coordinates: without them GolfCore reads the golfer's position from the GolfCore app on their phone. Both are GolfCore Premium: the golfer signs in to GolfCore once, and without Premium the result lists the plans for subscribe_premium. For everything else there is search: courses and their scorecards, the town, region and country pages that count and list every course in a place, and GolfCore's own product pages. Narrow it with scope when you know what you want: scope ['slug','scorecards'] with a course slug as the query returns that one exact card. When the person asks for courses near them, near a hotel or near a town you can locate, pass near with coordinates and courses come back nearest first with miles; add coverage 'contours' when they want green maps. To let the person see a course's map, give them the course's app_url, with &hole=N appended for a particular hole: it opens that course in the GolfCore app in any browser, and a guest can start without an account. Take par, stroke index, yardage, course rating and slope from a course's layouts, never from a page extract. Cite the url on anything you use.

Tools

9 advertised

search — Search GolfCore
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

Search everything GolfCore holds for more than 30,000 golf courses in more than 180 countries and territories. Ask by course name ('Pebble Beach'), by its name in local script ('宮崎カントリークラブ'), by architect ('Donald Ross'), by slug ('pebble-beach'), by place, passing just the place name ('St Andrews', 'Monterey'), or about GolfCore itself ('what does a caddie master use GolfCore for'). A course comes back with its address, town, region, country, coordinates, timezone, phone and website, its architect and the year it opened where known, and its name in Japanese or Korean script where that differs; flags for what GolfCore has mapped -- lidar green contours, a traced map of fairways, tees, greens, bunkers and water, a live wind grid, a scorecard, USGA ratings; and, when scope includes scorecards, its full card: par, yardage and stroke index for every hole, and yardage, par, course rating and slope rating for every tee, separately for men and women. Places come back as the town, region or country page that counts and lists every course there. Pages come from GolfCore's own site. Every result carries the url to cite, and a course's page carries the green figures this tool does not: greens mapped, contour count and interval, largest green elevation span, steepest measured slope, and tree canopy. For 'courses near me' or 'near this hotel', pass near with the person's coordinates: courses come back nearest first with their distance in miles, and query may be left empty. Each course also carries app_url, the link that opens that course's map in the GolfCore app, in a browser or on a phone, with no account needed to start; append &hole=N to open on a given hole.

search input schema
{
  "type": "object",
  "properties": {
    "near": {
      "type": "object",
      "required": [
        "lat",
        "lng"
      ],
      "properties": {
        "lat": {
          "type": "number",
          "maximum": 90,
          "minimum": -90
        },
        "lng": {
          "type": "number",
          "maximum": 180,
          "minimum": -180
        }
      },
      "description": "Optional. A point to search around, such as the person's location or their hotel. Courses come back nearest first, each with its distance in miles.",
      "additionalProperties": false
    },
    "limit": {
      "type": "integer",
      "description": "Results per scope. Default 5, maximum 20."
    },
    "query": {
      "type": "string",
      "description": "What you are looking for, in plain English. May be empty when near is given; with near, it filters courses by name or town."
    },
    "scope": {
      "type": "array",
      "items": {
        "enum": [
          "product",
          "country",
          "region",
          "city",
          "courses",
          "scorecards",
          "slug"
        ],
        "type": "string"
      },
      "description": "Optional. Narrow the search to these scopes: 'slug' treats the query as a GolfCore course slug and returns that exact course, 'courses' matches courses by name and town, 'scorecards' attaches each course's per-hole card and tee ratings to it, 'city', 'region' and 'country' return pages that count and list every course in a place, 'product' returns GolfCore's own pages. Omit to search all of them. Combine freely, e.g. [\"slug\",\"scorecards\"] for one exact card, or [\"city\",\"courses\"]. Leave 'scorecards' out when you only need to know which courses exist; the cards are large."
    },
    "coverage": {
      "enum": [
        "contours",
        "traced",
        "scorecard",
        "rated"
      ],
      "type": "string",
      "description": "Optional. Only courses GolfCore has this for: 'contours' lidar green contour maps, 'traced' a traced course map, 'scorecard' a hole-by-hole card, 'rated' USGA course and slope ratings."
    },
    "radius_miles": {
      "type": "number",
      "description": "Optional, with near. How far to look, in miles. Default 25, maximum 250."
    }
  },
  "additionalProperties": false
}
search annotations
{
  "title": "Search GolfCore",
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}
distance_to_flag — Distance to the flag
Advertised by the server during the last successful anonymous check.
Advertised read-only

How far the golfer is from the flag, from where they are standing: 'how far is that flag', 'what's the yardage'. Returns the course, the hole, its par and stroke index, and yards to the flag (today's pin as the club set it) and to the middle of the green. Pass lat and lng only if your device gives you the golfer's GPS position; otherwise call it with no arguments, and GolfCore reads the golfer's position from the GolfCore app on their phone. It is part of GolfCore Premium: the golfer signs in to GolfCore the first time, and without Premium the result lists the plans for subscribe_premium. position_age_s says how old that position is. When hole_inferred is true the hole was chosen from the position, so say which hole you assumed.

distance_to_flag input schema
{
  "type": "object",
  "properties": {
    "lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Optional. The golfer's precise latitude, only when your device gives you their GPS position. Never ask the golfer for coordinates: leave lat and lng out and GolfCore uses the position from the GolfCore app on their phone."
    },
    "lng": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Optional. The golfer's precise longitude, with lat."
    },
    "hole": {
      "type": "string",
      "description": "Optional. The hole number the golfer says they are on. Otherwise the hole is chosen from the position."
    },
    "course": {
      "type": "string",
      "description": "Optional. The course slug, when known. Otherwise the course is found from the position."
    },
    "accuracy_m": {
      "type": "number",
      "description": "Optional. The location's horizontal accuracy in meters, when the device reports it."
    }
  },
  "additionalProperties": false
}
distance_to_flag annotations
{
  "title": "Distance to the flag",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
ask_caddie — Ask the GolfCore caddie
Advertised by the server during the last successful anonymous check.

Ask GolfCore's caddie a question about the shot the golfer is standing over, such as which club to hit or where to aim. Pass the question in their words, and lat and lng only if your device gives you their GPS position; otherwise GolfCore uses the position from the GolfCore app on their phone. The caddie reads the distance to the flag, the hazards and trees on the line, wind modeled for the terrain, the elevation change, and the golfer's own handicap and club distances from their GolfCore account, and answers with a club and a line; the golfer signs in to GolfCore the first time. It needs GolfCore Premium; without it the result lists the plans, and subscribe_premium starts one.

ask_caddie input schema
{
  "type": "object",
  "required": [
    "question"
  ],
  "properties": {
    "lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Optional. The golfer's precise latitude, only when your device gives you their GPS position. Never ask the golfer for coordinates: leave lat and lng out and GolfCore uses the position from the GolfCore app on their phone."
    },
    "lng": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Optional. The golfer's precise longitude, with lat."
    },
    "hole": {
      "type": "string",
      "description": "Optional. The hole number the golfer says they are on. Otherwise the hole is chosen from the position."
    },
    "course": {
      "type": "string",
      "description": "Optional. The course slug, when known. Otherwise the course is found from the position."
    },
    "question": {
      "type": "string",
      "description": "The golfer's question, in their words."
    },
    "accuracy_m": {
      "type": "number",
      "description": "Optional. The location's horizontal accuracy in meters, when the device reports it."
    }
  },
  "additionalProperties": false
}
ask_caddie annotations
{
  "title": "Ask the GolfCore caddie",
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}
subscribe_premium — Subscribe to GolfCore Premium
Advertised by the server during the last successful anonymous check.
Open-world

Create a GolfCore Premium checkout link for the signed-in golfer. Premium adds the caddie in this connector and the GolfCore app, plus green contour maps, live wind and offline course packs. Plans: day_pass, $3 for 24 hours of Premium, one charge and no subscription, the popular choice for a golfer on the course today; plus_monthly, $10 a month; and plus_yearly, $100 a year. A first-time subscriber pays half for the first month or first year. Ask the golfer which plan they want before calling. Returns a secure Stripe checkout URL and the current plan terms. Give the link to the golfer to review and pay; this tool does not charge them or activate Premium.

subscribe_premium input schema
{
  "type": "object",
  "required": [
    "plan"
  ],
  "properties": {
    "plan": {
      "enum": [
        "day_pass",
        "plus_monthly",
        "plus_yearly"
      ],
      "type": "string",
      "description": "The plan the golfer chose."
    }
  },
  "additionalProperties": false
}
subscribe_premium annotations
{
  "title": "Subscribe to GolfCore Premium",
  "readOnlyHint": false,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": false
}
api_account — Read GolfCore API account
Advertised by the server during the last successful anonymous check.
Advertised read-only

For a developer using the GolfCore Course Data API: list the API accounts the signed-in person can see, or read one with its plan, this month's usage, monthly cap if one is set, and keys (prefixes only, never secrets). Use it before the other api_ tools to get account_id and key_id. Plans: free, 500 requests a month at 10 a minute; basic, $10 a month for 10,000 at 60 a minute, then $2.00 per 1,000; business, $50 a month for 100,000 at 300 a minute, then $1.00 per 1,000. Paid plans have no monthly cap unless the person sets one. If the person has no account, they create one at https://platform.golfcore.app.

api_account input schema
{
  "type": "object",
  "properties": {
    "account_id": {
      "type": "integer",
      "description": "Optional. One account's detail; omit to list all."
    }
  },
  "additionalProperties": false
}
api_account annotations
{
  "title": "Read GolfCore API account",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
api_create_key — Create a GolfCore API key
Advertised by the server during the last successful anonymous check.

Create a GolfCore Course Data API key for the signed-in person's account. Returns the secret once; hand it to the person to store in their server's configuration, and never put it in chat logs, code, a mobile app or browser code. Confirm the name with the person first.

api_create_key input schema
{
  "type": "object",
  "required": [
    "account_id",
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "What the key is for, such as the server or app."
    },
    "expiry": {
      "enum": [
        "30_days",
        "90_days",
        "1_year",
        "never"
      ],
      "type": "string",
      "description": "Default 90_days."
    },
    "account_id": {
      "type": "integer",
      "description": "From api_account."
    }
  },
  "additionalProperties": false
}
api_create_key annotations
{
  "title": "Create a GolfCore API key",
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}
api_revoke_key — Revoke a GolfCore API key
Advertised by the server during the last successful anonymous check.
Advertised destructive

Revoke one of the signed-in person's GolfCore API keys. Requests with it are refused within about a minute, and it cannot be restored. Confirm the key's name and prefix with the person before calling.

api_revoke_key input schema
{
  "type": "object",
  "required": [
    "account_id",
    "key_id"
  ],
  "properties": {
    "key_id": {
      "type": "integer",
      "description": "From api_account's keys."
    },
    "account_id": {
      "type": "integer",
      "description": "From api_account."
    }
  },
  "additionalProperties": false
}
api_revoke_key annotations
{
  "title": "Revoke a GolfCore API key",
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": true
}
api_upgrade — Upgrade a GolfCore API plan
Advertised by the server during the last successful anonymous check.
Open-world

Start an upgrade of the signed-in person's GolfCore API account to basic ($10 a month for 10,000 requests, then $2.00 per 1,000) or business ($50 a month for 100,000, then $1.00 per 1,000). Returns a Stripe checkout URL for the person to review and pay; this tool does not charge them. If the account already has a paid plan it returns the billing page, where the person switches plans themselves. Ask which plan they want first.

api_upgrade input schema
{
  "type": "object",
  "required": [
    "account_id",
    "plan"
  ],
  "properties": {
    "plan": {
      "enum": [
        "basic",
        "business"
      ],
      "type": "string"
    },
    "account_id": {
      "type": "integer",
      "description": "From api_account."
    }
  },
  "additionalProperties": false
}
api_upgrade annotations
{
  "title": "Upgrade a GolfCore API plan",
  "readOnlyHint": false,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": false
}
api_budget — Set or remove the GolfCore API monthly cap
Advertised by the server during the last successful anonymous check.

Starter and Pro have no monthly cap by default: requests past the included amount are billed at the plan's overage rate without limit. This tool sets an optional cap, after which requests are refused until the month resets, or removes it when units is null. A cap starts at the plan's included requests (read them from api_account). Confirm the number and what it could cost with the person first.

api_budget input schema
{
  "type": "object",
  "required": [
    "account_id",
    "units"
  ],
  "properties": {
    "units": {
      "type": [
        "integer",
        "null"
      ],
      "minimum": 1,
      "description": "Monthly request cap, or null for no cap."
    },
    "account_id": {
      "type": "integer",
      "description": "From api_account."
    }
  },
  "additionalProperties": false
}
api_budget annotations
{
  "title": "Set or remove the GolfCore API monthly cap",
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

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
265 ms
95th percentile latency
265 ms

Maintenance history

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

  • · probe · passed · 265 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 golfcore-mcp https://mcp.golfcore.org/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 golfcore-mcp --url https://mcp.golfcore.org/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable golfcore-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "golfcore-mcp": {
      "url": "https://mcp.golfcore.org/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "golfcore-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.golfcore.org/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start golfcore-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "golfcore-mcp": {
      "type": "http",
      "url": "https://mcp.golfcore.org/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 golfcore-mcp https://mcp.golfcore.org/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://mcp.golfcore.org/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": {
    "golfcore-mcp": {
      "serverUrl": "https://mcp.golfcore.org/mcp"
    }
  }
}

Let your agent find its tools

Find servers like GolfCore 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
See all 5,943

Do you run GolfCore 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