Ask Claude about golf club specs with the GolfAPI.dev connector
Add the GolfAPI.dev MCP server at mcp.golfapi.dev to claude.ai as a custom connector, or to any MCP client. A free key reads every 2025 and 2026 driver.
ReadPosts tagged How-to
GolfAPI.dev blog posts tagged How-to: 7 posts, newest first.
Keep a golf club database current with a nightly GET /changes job
Store the release header from your last full scan, ask GET /changes what each later release added, updated or removed, and refetch only those clubs.
Read
Read golf club launch prices (MSRP) with view=market
intro_price is a club's launch MSRP per market, in minor units. Read it with view=market, filter with msrp_min and msrp_max, and keep markets apart.
Read
60% of right-handed 5-woods have an 18° head
The exceptions run from 17.5° low-spin heads to 23° women's models, a higher loft than the median 7-wood. Compare fairway woods by loft_deg.
Read
Handle missing golf club specs in API responses
A missing field, a false value and a field you did not request are three different states. Keep them apart in code, in filters and in agent instructions.
Read
Build a driver comparison page with stable club IDs
Save the drivers a user picks by clb_ id, fetch them by id, compare variants instead of lofts_deg and hands, and keep a saved club that returns 404.
Read
Your first golf club API request with curl
Request one driver from GET /drivers with a test key, read the record and its headers, then narrow the response with fields= and a manufacturer filter.
Read