Ask Claude about golf clubs, with the makers' published specs

Connect a client

Every client asks for a GolfAPI.dev API key. Get a free key in the Console first: it starts with sk_test_ and reads the sandbox sample. A sk_live_ key reads the catalog your plan covers.

Then follow the steps for your client.

claude mcp add --transport http golfapi https://mcp.golfapi.dev \
  --header "Authorization: Bearer $GOLFDEV_API_KEY"

[mcp_servers.golfapi]
url = "https://mcp.golfapi.dev"
bearer_token_env_var = "GOLFDEV_API_KEY"

{
  "mcpServers": {
    "golfapi": {
      "url": "https://mcp.golfapi.dev",
      "headers": {
        "Authorization": "Bearer ${env:GOLFDEV_API_KEY}"
      }
    }
  }
}

{
  "inputs": [
    {
      "type": "promptString",
      "id": "golfapi-key",
      "description": "GolfAPI.dev API key",
      "password": true
    }
  ],
  "servers": {
    "golfapi": {
      "type": "http",
      "url": "https://mcp.golfapi.dev",
      "headers": {
        "Authorization": "Bearer ${input:golfapi-key}"
      }
    }
  }
}

Try these prompts

Copy a prompt into a chat with GolfAPI.dev turned on. Each one names the plan its key needs.

• Which 2026 drivers come in 12 degrees for left-handed players?

  Free keyCopy

• List every 2025 driver from Callaway with its launch price.

  Free keyCopy

• What changed between the TaylorMade Qi35 and Qi4D drivers?

  Free keyCopy

• Which 2025 and 2026 drivers have an adjustable hosel and cost under $550 at launch?

  Free keyCopy

• What is the 7-iron loft of each Mizuno JPX925 iron set?

  Needs HobbyCopy

• What was the US launch price of the TaylorMade SIM2 driver?

  Needs ProCopy

What each plan reads

Prices and limits are on Pricing. Field coverage per club type is on Catalog.

Build with it

1. Add the server to Claude Code, Cursor, VS Code or Codex with the steps above.
2. Ask the agent to build the feature, such as a driver selector that filters by loft and hand. It reads the real routes, fields and records while it writes the code.
3. Run what it writes against the sandbox sample with a sk_test_ key.
4. Shipping it to your users needs Pro.

Write with it

1. Connect Claude or ChatGPT with the steps above.
2. Ask for a table, such as the lofts, head volume and launch price of every 2026 driver from one maker.
3. Fields a maker did not publish stay empty in the table.
4. Publishing what the assistant writes needs Pro.

How it behaves

• The server is read-only. Each tool sends one GET to https://api.golfapi.dev with your API key.
• A tool call counts as one request against your plan, the same as a REST request.
• A field missing from a club has no published value from its maker. The server tells the assistant not to fill it from another club, hand or loft. A 0 or false is a real value.
• A sk_test_ key reads the sandbox sample. A sk_live_ key reads the whole catalog your plan covers.
• Revoke the key in the Console to disconnect every client that uses it. Create one key per client to disconnect them one at a time.
• Connections made to https://mcp.golfapi.dev/mcp keep working.

The six tools

describe_api

Lists the club types, routes, response version, what your key can read and the catalog build it reads.

search_clubs

Lists clubs of one type, filtered by text, maker, family, release year, hand, loft or adjustable hosel. Price filters need Pro.

get_club

Returns one club's document by clb_ ID or slug, optionally narrowed to one hand or loft.

get_coverage

Counts clubs per maker and release year, and how many clubs carry each field.

get_changes

Lists the catalog releases after a build you already read, with each club added, updated, corrected or removed.

api_get

Sends a GET to any API path, for routes the other tools do not cover.

Tool arguments, errors and quota are in the MCP server reference.

Questions

• Which apps does it work with?

  Any MCP client that speaks Streamable HTTP. This page has steps for Claude, Claude Desktop, Claude Code, ChatGPT, Cursor, VS Code and Codex.

• Is it free?

  A free key reads the sandbox sample of 2025 and 2026 drivers. Older drivers and the other club types need Hobby or Pro.

• Can I publish what Claude writes?

  Yes, on Pro. Free covers testing and building an integration, and Hobby covers personal, non-commercial use.

• Does it see my chats?

  No. The server receives tool calls, each a GET with your key, and nothing else from the conversation.

• How current is the free sample?

  The sample is a copy of the signed 2025 and 2026 driver files, refreshed by hand rather than with each catalog release. A driver corrected after the last refresh keeps its earlier values in the sample until the next one. describe_api names the catalog build your key reads.