Permite que un cliente de IA acceda a datos propietarios de campos de golf, incluyendo tarjetas de puntuación, coordenadas GPS e imágenes 3D de la pendiente de los greens.
También conocido como golf-data/golf, golf
- Stars
- 4
- Herramientas
- 5
- Descargas, 30 días
- —
- Última versión
- 1.0.7
- Último commit
- 31 oct 2026
- Licencia
- MIT
¿Qué es Golf Course Data by Stracka MCP?
Permite que un cliente de IA acceda a datos propietarios de campos de golf, incluyendo tarjetas de puntuación, coordenadas GPS e imágenes 3D de la pendiente de los greens. Expone 5 herramientas, como search_course_groups, get_course_group_scorecard, get_course_group_gps.
Resumen generado a partir del README del proyecto
Acerca del MCP server de Golf Course Data by Stracka
Es posible acceder a información propietaria de campos de golf a través de un cliente de IA con este servidor. Proporciona a desarrolladores y entusiastas del golf datos actualizados diariamente, como tarjetas de puntuación, coordenadas GPS e imágenes 3D de la pendiente de los greens. El servidor funciona mediante una conexión MCP alojada a través de streamable HTTP o como un servidor stdio local para desarrollo offline.
Los usuarios deben configurar la conexión utilizando un Client ID y un Active Token obtenidos de una cuenta de Golf Intelligence. El servicio opera con un sistema basado en créditos con diferentes planes mensuales, como el plan Tester para 100 créditos o el plan Starter para 10,000 créditos. Para evitar costes accidentales, el servidor requiere una confirmación explícita antes de ejecutar cualquier herramienta de pago como get_course_group_gps o get_green_slope_image.
Aunque la búsqueda de grupos de campos es gratuita, otras consultas de datos específicos consumen créditos. El sistema está diseñado para ser seguro, intercambiando credenciales por tokens de portador de corta duración que solo se almacenan en caché en la memoria. Es compatible con varios entornos, incluyendo Cursor, Claude Code y ChatGPT a través de OAuth 2.1.
Qué puedes hacer con él
- 1Recuperar tarjetas de puntuación del campoPide a la IA que obtenga datos específicos de la tarjeta de puntuación para un grupo de campos de golf en particular.
- 2Analizar la topografía del greenSolicita una imagen 3D de la pendiente del green para entender el terreno de un hoyo específico.
- 3Mapear la geometría del campoUtiliza la IA para obtener la geometría mapeada del campo y las coordenadas GPS.
- 4Buscar campos de golfBusca grupos de campos específicos sin consumir créditos de la cuenta.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar Golf Course Data by Stracka MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar Golf Course Data by Stracka MCP en Claude Code
$ claude mcp add --transport http golf https://mcp.golfintelligence.com/mcpInstalar Golf Course Data by Stracka MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"golf": {
"url": "https://mcp.golfintelligence.com/mcp"
}
}
}Instalar Golf Course Data by Stracka MCP en VS Code
.vscode/mcp.json
{
"servers": {
"golf": {
"type": "http",
"url": "https://mcp.golfintelligence.com/mcp"
}
}
}Instalar Golf Course Data by Stracka MCP en VS Code CLI
$ code --add-mcp '{"name":"golf","type":"http","url":"https://mcp.golfintelligence.com/mcp"}'Instalar Golf Course Data by Stracka MCP en Codex
$ codex mcp add golf --url https://mcp.golfintelligence.com/mcpInstalar Golf Course Data by Stracka MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.golf] url = "https://mcp.golfintelligence.com/mcp"
Instalar Golf Course Data by Stracka MCP en Gemini CLI
$ gemini mcp add -s user --transport http golf https://mcp.golfintelligence.com/mcpInstalar Golf Course Data by Stracka MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"golf": {
"url": "https://mcp.golfintelligence.com/mcp",
"type": "http"
}
}
}Herramientas de Golf Course Data by Stracka MCP 5
Detectado desde el READMEsearch_course_groupsget_course_group_scorecardget_course_group_gpsget_course_group_detailget_green_slope_image
| search_course_groups | — | |
| get_course_group_scorecard | — | |
| get_course_group_gps | — | |
| get_course_group_detail | — | |
| get_green_slope_image | — |
Configuración
GI_ACTIVE_TOKENObligatorioSecretoActive Token from API Account at console.golfintelligence.com. It is exchanged for a bearer token; do not enter a bearer token.
GI_CLIENT_IDObligatorioClient ID from API Account at console.golfintelligence.com.
| Nombre | Descripción | Tipo |
|---|---|---|
| GI_ACTIVE_TOKEN | Active Token from API Account at console.golfintelligence.com. It is exchanged for a bearer token; do not enter a bearer token. | ObligatorioSecreto |
| GI_CLIENT_ID | Client ID from API Account at console.golfintelligence.com. | Obligatorio |
Verificaciones automáticas
Ejecutado 12 nov 2026Informe completo →Pasó nuestras verificaciones automáticas. Esto no es una auditoría de seguridad: lee el código y dale al servidor el acceso más limitado que necesite. Cómo funcionan las verificaciones
- Repositorio de origen vinculado y accesibleAprobado
- Licencia de código abierto (OSI)Aprobado
- Commit o lanzamiento en el último añoAprobado
- El nombre del paquete no es similar a un paquete popularNo verificado
- El endpoint remoto usa HTTPSAprobado
- Las herramientas destructivas están etiquetadasAprobado
- Sin instrucciones ocultas para el modeloAprobado
- No hay avisos críticos en el paquete ni en sus dependenciasNo verificado
README
Ver en GitHubGolf Course Data by Stracka
Golf Course Data by Stracka. Proprietary StrackaGolf course data only, updated daily. Search is free. Scorecards, GPS, and 3D greens via API.
Golf Intelligence provides proprietary StrackaGolf course data, updated daily. Learn more at golfintelligence.com.
This repository is the installable Cursor / Grok Bot plugin with handle
golf. The Cursor marketplace application source is the public GitHub URL:
https://github.com/golf-data/golf
Marketplace reviewers can submit that URL at cursor.com/marketplace/publish. The catalog title is Golf Course Data by Stracka.
The bundled mcp.json connects to the hosted MCP at
https://mcp.golfintelligence.com/mcp over Streamable HTTP, so installing the
plugin never depends on a local Node build. Your console credentials travel as
the X-GI-Client-ID and X-GI-Active-Token headers, filled from the plugin
variables declared in .cursor-plugin/plugin.json.
Earlier releases launched node against a plugin-relative dist/index.js.
Cursor does not expand the Agent Plugins ${PLUGIN_ROOT} variable, so that
placeholder reached Node literally and the connector failed with
Cannot find module '.../${PLUGIN_ROOT}/dist/index.js'. The hosted connector
removes that failure mode entirely.
mcp.stdio.json keeps the local stdio server for offline and development use.
It is not auto-discovered; copy its golf entry into .cursor/mcp.json (using
${workspaceFolder} in a checkout) or point mcpServers at it. Any local
stdio config must use ${CURSOR_PLUGIN_ROOT}, never ${PLUGIN_ROOT}. The
committed dist/index.js bundle ships in the repository and in the MCPB
package, so the stdio path works without running a build first.
The official MCP Registry name is io.github.golf-data/golf. The registry
does not accept a bare golf name. Cursor, Agent Plugins, and Claude Code
plugin handles remain golf.
Get API access
Sign in at console.golfintelligence.com without a password: enter your email on the login page, request a verification code, then enter the code after it is sent. Create an API Account and configure the plugin's two required variables:
GI_CLIENT_ID: your Client IDGI_ACTIVE_TOKEN: your Active Token
The Active Token is exchanged for a short-lived bearer token. It is not a
bearer token; do not paste a bearer token into GI_ACTIVE_TOKEN.
Use credentials from your own console account. This project does not provide demo tokens.
Plans are monthly and can be upgraded or downgraded self-serve in the console:
- Tester: $49/month for 100 credits/month.
- Starter: $399/month for 10,000 credits/month.
For billing, credits, plans, login, or credential help, email support@golfintelligence.com. For course data updates, email data@golfintelligence.com.
Tools and credits
Always search first. search_course_groups is free. Before every paid call,
the user must explicitly confirm the stated cost; the server refuses paid tools
unless confirm_spend=true.
| Tool | What it returns | Credits |
|---|---|---|
search_course_groups |
Course-group search results | 0 |
get_course_group_scorecard |
Scorecard data | 1 |
get_course_group_gps |
Mapped course geometry and coordinates | 2 |
get_course_group_detail |
Detailed course-group data | 3 |
get_green_slope_image |
Portrait or square green slope image | 1 |
Authentication
The local stdio server and legacy per-user HTTP credential headers exchange the configured credentials with:
POST https://api.golfintelligence.com/auth/authenticateToken
grant_type=client_credentials
code=<GI_ACTIVE_TOKEN>
client_id=<GI_CLIENT_ID>
It sends the returned access_token as Authorization: Bearer <access_token>,
caches it only in memory, and refreshes once after an HTTP 401. Credentials are
never logged.
The hosted MCP additionally implements OAuth 2.1 authorization-code flow with S256 PKCE for ChatGPT. Its dedicated authorization page accepts each user's own console Client ID and Active Token, validates them with Golf Intelligence, and binds that account to encrypted access and refresh tokens. See docs/OPENAI-CHATGPT-OAUTH.md for discovery URLs, OpenAI portal settings, reviewer steps, and deployment secrets.
Streamable HTTP
The hosted MCP is available via the official MCP Streamable HTTP transport at:
https://mcp.golfintelligence.com/mcp
The production HTTP entrypoint serves that transport at /mcp and a health
check at /health. For OpenAI Apps domain verification it also serves
GET /.well-known/openai-apps-challenge as text/plain when
OPENAI_APPS_CHALLENGE_TOKEN (or OPENAI_APPS_CHALLENGE) is set; otherwise
that path returns 404. Start the HTTP server locally with:
npm run build
PORT=3000 npm run start:http
It binds to 0.0.0.0:$PORT. The existing node dist/index.js stdio entrypoint
and all plugin packages remain unchanged.
The HTTP service accepts Golf Intelligence identity in either of these forms:
- An OAuth bearer token issued by this service after the user signs in with their own GI account.
- Legacy
X-GI-Client-IDandX-GI-Active-Tokenheaders supplied together on every MCP request by existing plugin installs.
There is deliberately no server-wide GI_CLIENT_ID / GI_ACTIVE_TOKEN
fallback. The HTTP entrypoint ignores those environment variables, so an
anonymous caller cannot inherit a deployment account or spend its credits.
Missing or invalid OAuth returns HTTP 401 with an OAuth protected-resource
challenge. The Active Token is an exchange credential and must not be sent as
an Authorization: Bearer value.
Every tool explicitly advertises these MCP annotations:
readOnlyHint: true— each tool only retrieves course data.openWorldHint: false— no tool writes to public or external systems.destructiveHint: false— no tool deletes, overwrites, publishes, or sends anything.idempotentHint: truefor free search.idempotentHint: falsefor paid tools because every repeated paid invocation can consume credits again.
These sentences can also be used as the annotation justifications in the
OpenAI submission form. Paid lookups still require confirm_spend=true at the
same credit costs documented above.
Container deployment
Dockerfile builds both transports without embedding credentials.
fly.toml configures a small Fly.io service and checks /health. Before the
first deploy, confirm that the globally unique Fly app name is available (or
change app), then configure the OAuth secrets documented in
docs/OPENAI-CHATGPT-OAUTH.md and deploy. At minimum:
fly volumes create oauth_state --region ord --size 1
fly secrets set OAUTH_ENCRYPTION_KEY="$(openssl rand -base64 32)"
fly secrets set OAUTH_ISSUER=https://mcp.golfintelligence.com
fly secrets set OPENAI_APPS_CHALLENGE_TOKEN=...
fly deploy
The mounted volume stores OAuth replay/rotation state, not GI credentials. Run one Machine for this file-backed state store.
Do not configure a shared GI account for hosted HTTP callers. If
GI_CLIENT_ID / GI_ACTIVE_TOKEN exist for a separate bootstrap or stdio
workflow, they do not authorize HTTP requests.
Set OPENAI_APPS_CHALLENGE_TOKEN to the token shown in OpenAI Platform domain
verification. Do not commit that token. After deploy,
GET https://mcp.golfintelligence.com/.well-known/openai-apps-challenge
should return the token as text/plain.
Tool names and descriptions are baked into the deployed bundle, so the hosted
MCP keeps serving the previous copy until it is redeployed. Redeploy before
refreshing the marketplace listing, and follow docs/RELEASE.md for the full
order across Fly, the marketplace, and the MCP Registry.
Repository layout
.cursor-plugin/plugin.json— Cursor marketplace manifest and required variablesplugin.json— Agent Plugins open-standard manifest (handlegolf).claude-plugin/plugin.json— Claude Code / Cowork plugin manifest (handlegolf)server.json— official MCP Registry metadata (io.github.golf-data/golf)manifest.json— MCPB bundle manifest for the stdio Node server.github/workflows/publish-mcp.yml— publishesio.github.golf-data/golfto the official MCP Registry via GitHub OIDCmcp.json— bundledgolfconnector pointing at the hosted MCP endpointmcp.stdio.json— optional local stdio configuration for offline developmentskills/golf/SKILL.md— workflow and spend-confirmation guidancedocs/SMOKE-CHECKLIST.md— post-deploy and post-publish verification stepsdocs/RELEASE.md— Fly redeploy, GitHub release, and registry publish runbooksrc/— TypeScript MCP server and API clientdist/index.js— committed stdio ESM bundle used by installersdist/http.js— committed Streamable HTTP ESM bundle used by the containerDockerfileandfly.toml— production HTTP container and Fly.io service
For development with Node.js 18 or newer:
npm install
npm test
npm run build
npm run pack:mcpb
pack:mcpb uses the official @anthropic-ai/mcpb pack CLI to produce golf.mcpb and writes its SHA-256 into server.json. GitHub Releases host that asset at https://github.com/golf-data/golf/releases/download/v1.0.2/golf.mcpb.
The plugin code is available under the MIT License. Golf Intelligence API data remains subject to the terms at golfintelligence.com.
Preguntas sobre Golf Course Data by Stracka MCP
¿Cómo agrego Golf Course Data by Stracka MCP a Claude Code?
Ejecuta claude mcp add --transport http golf https://mcp.golfintelligence.com/mcp en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego Golf Course Data by Stracka MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Qué herramientas proporciona Golf Course Data by Stracka MCP?
Expone 5 herramientas, incluidas search_course_groups, get_course_group_scorecard, get_course_group_gps, get_course_group_detail, get_green_slope_image.
¿Cuánto cuesta usar la API?
Los precios se basan en planes mensuales: el plan Tester cuesta $49/mes por 100 créditos, y el plan Starter cuesta $399/mes por 10,000 créditos.