# Golf Intelligence, by Stracka [Health: Active]

**Category:** 🚀 Aerospace & Astrodynamics  
**Repository:** https://github.com/golf-data/golf  
**GitHub Stars:** 2  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/golf-intelligence-by-stracka

## Description
Proprietary mapped golf courses (laser, drone, satellite). 20 years, daily updates. Search is free.

## Tools
Capabilities this server exposes over MCP:

- **search_course_groups** — 0
- **get_course_group_scorecard** — 1
- **get_course_group_gps** — 2
- **get_course_group_detail** — 3
- **get_green_slope_image** — 1

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "golf-intelligence-by-stracka": {
    "url": "https://mcp.golfintelligence.com/mcp"
  }
}
```

## Documentation

## What Golf Intelligence, by Stracka does

Golf Intelligence, by Stracka exposes daily-updated StrackaGolf course data through MCP. The service is intended for developers building golf applications or agents that need course discovery and mapped course information.

Available data includes course-group search results, scorecards, GPS geometry and coordinates, detailed course-group records, and portrait or square images showing green slopes. The underlying course coverage is based on proprietary mapping from laser, drone, and satellite sources, according to the project description.

## How it works

The normal hosted connection uses the Streamable HTTP endpoint at `https://mcp.golfintelligence.com/mcp`. Existing plugin installations can provide `X-GI-Client-ID` and `X-GI-Active-Token` headers with each request. The hosted service also supports OAuth 2.1 authorization-code authentication with S256 PKCE for supported ChatGPT deployments.

A local Node.js stdio entrypoint is also included. Its client configuration can be copied into a client MCP configuration file, and the committed `dist/index.js` bundle means a build is not required before using that path.

Authentication exchanges the configured Client ID and Active Token for a short-lived bearer token. The Active Token is an exchange credential, not a bearer token, and should not be placed in an `Authorization` header. Access tokens are cached in memory and refreshed after an HTTP 401 response.

## Setup and configuration

Create an account through the Golf Intelligence console, create an API Account, and configure these variables for the local stdio workflow:

- `GI_CLIENT_ID`: the console Client ID
- `GI_ACTIVE_TOKEN`: the console Active Token

The project does not provide demo credentials. Plans use monthly credits; the documented Tester plan includes 100 credits per month for $49, and the Starter plan includes 10,000 credits per month for $399.

For local HTTP development, build the project and start the HTTP entrypoint with `npm run build` followed by `npm run start:http`. The service listens on `0.0.0.0:$PORT`. Hosted OAuth deployments require additional issuer, encryption, and OpenAI verification configuration described by the repository documentation.

## Tools and capabilities

Golf Intelligence, by Stracka provides these tools:

- `search_course_groups` searches course groups at no credit cost.
- `get_course_group_scorecard` returns scorecard data for 1 credit.
- `get_course_group_gps` returns mapped geometry and coordinates for 2 credits.
- `get_course_group_detail` returns detailed course-group data for 3 credits.
- `get_green_slope_image` returns a portrait or square green-slope image for 1 credit.

The intended workflow is to search first, identify the relevant course group, and then request additional data. Paid calls require `confirm_spend=true`; the server rejects them without that confirmation. Repeating a paid call can consume credits again.

## Limitations and notes

The tools retrieve data only. They do not write to external systems, publish content, delete records, or modify course data. Search is free, but scorecard, GPS, detail, and green-slope requests consume account credits.

The hosted HTTP service does not use a server-wide fallback account. Requests must carry a valid OAuth token or the legacy Golf Intelligence identity headers. Do not deploy shared credentials for hosted callers. Tool descriptions are bundled into the deployed server, so changes require redeployment before hosted clients receive them.

_Full upstream README: https://allmcps.com/mcp/golf-intelligence-by-stracka/readme_