---
title: "Ask Claude about golf clubs, with the makers' published specs"
description: "Connect Claude, Codex, Grok, Cursor, VS Code or ChatGPT to the GolfAPI.dev MCP server and ask about golf club specifications with your API key."
url: "https://golfapi.dev/mcp"
server: "https://mcp.golfapi.dev"
---

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

Connect GolfAPI.dev to Claude, Codex, Grok, Cursor or ChatGPT. Your assistant looks up clubs in the catalog with your API key and reads the specifications each maker published.

A free key covers every 2025 and 2026 driver in the sandbox sample: 66 models from 11 makers, 63 with a US launch price.

Server address:

```
https://mcp.golfapi.dev
```

Get a free key: https://console.golfapi.dev/?plan=free

## 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. Free key: https://console.golfapi.dev/?plan=free

### Claude

Add to Claude: https://claude.ai/settings/connectors

1. In claude.ai, open Settings, then Connectors.
2. Choose Add custom connector. Name it GolfAPI.dev and paste `https://mcp.golfapi.dev` as the URL.
3. Choose Connect. A GolfAPI.dev page opens and asks for an API key.
4. Paste your API key, which starts with `sk_test_` or `sk_live_`, and choose Connect. The `key_` ID does not work here.
5. In a new chat, turn on GolfAPI.dev in the tools menu and ask a question.
6. The connector also appears in Claude Desktop and the Claude mobile apps when you sign in with the same account.

### Claude Code

1. In a terminal, run `export GOLFDEV_API_KEY='sk_test_your_key'` with your API key between the quotes.
2. Run the command below in the same terminal. Leave `$GOLFDEV_API_KEY` as written; the shell replaces it with your key.
3. Start `claude` and run `/mcp` to check that golfapi is connected.

Shell:

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

### Codex

1. Add the lines below to `~/.codex/config.toml`.
2. Set `GOLFDEV_API_KEY` to your API key in the environment Codex starts from.
3. Start `codex` and run `/mcp` to check that golfapi is listed.

~/.codex/config.toml:

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

### Grok

Add to Grok: https://grok.com/connectors

1. In Grok, open grok.com/connectors. Custom connectors need a paid Grok plan.
2. Choose New Connector, then Custom. Name it GolfAPI.dev, paste `https://mcp.golfapi.dev` as the server URL and choose Add Connector.
3. A GolfAPI.dev page opens and asks for an API key. Paste your API key, which starts with `sk_test_` or `sk_live_`, and choose Connect.
4. In a new chat, turn on GolfAPI.dev and ask a question.

### Cursor

Add to Cursor: cursor://anysphere.cursor-deeplink/mcp/install?name=golfapi&config=eyJ1cmwiOiJodHRwczovL21jcC5nb2xmYXBpLmRldiJ9

1. Choose Add to Cursor, or add the JSON below to `~/.cursor/mcp.json` for every project or `.cursor/mcp.json` for one.
2. With the button, Cursor opens a GolfAPI.dev page that asks for your API key. With the JSON, set `GOLFDEV_API_KEY` in the environment Cursor starts from.
3. Open Cursor Settings, then MCP, and check that golfapi lists six tools.

~/.cursor/mcp.json:

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

### VS Code

Add to VS Code: vscode:mcp/install?%7B%22name%22%3A%22golfapi%22%2C%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.golfapi.dev%22%7D

1. Choose Add to VS Code, or save the JSON below as `.vscode/mcp.json` in your project.
2. Start golfapi from the MCP servers list. With the JSON, VS Code asks for your API key once. With the button, a GolfAPI.dev page asks for it.
3. In Chat, choose Agent mode. The six golfapi tools appear in the tools list.

.vscode/mcp.json:

```json
{
  "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}"
      }
    }
  }
}
```

### ChatGPT

1. In ChatGPT, open Settings, then Apps & Connectors, then Advanced settings, and turn on Developer mode.
2. Back in Apps & Connectors, choose Create. Name it GolfAPI.dev, paste `https://mcp.golfapi.dev` as the server URL and choose OAuth for authentication.
3. Choose Create. A GolfAPI.dev page opens. Paste your API key and choose Connect.
4. In a new chat, add GolfAPI.dev from the tools menu and ask a question.

## 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 key)
- List every 2025 driver from Callaway with its launch price. (Free key)
- What changed between the TaylorMade Qi35 and Qi4D drivers? (Free key)
- Which 2025 and 2026 drivers have an adjustable hosel and cost under $550 at launch? (Free key)
- What is the 7-iron loft of each Mizuno JPX925 iron set? (Needs Hobby)
- What was the US launch price of the TaylorMade SIM2 driver? (Needs Pro)

## What each plan reads

- Free: The 2025 and 2026 drivers in the sandbox sample: 66 models, 63 with a US launch price. Testing GolfAPI.dev and building an integration.
- Hobby: All 7 club types, 2,319 models, specifications only. Personal, non-commercial use.
- Pro: Everything in Hobby, plus US launch prices. Commercial use, including publishing what your assistant writes.

Prices and limits are on Pricing: https://golfapi.dev/pricing/. Field coverage per club type is on Catalog: https://golfapi.dev/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: https://golfapi.dev/docs/mcp/

## 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.

## Connect now

Paste this address into your client, then sign in with your API key.

```
https://mcp.golfapi.dev
```

Get a free key: https://console.golfapi.dev/?plan=free