Open Golf Handicap MCP
Related Servers
Alternatives to Open Golf Handicap MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI applications to retrieve GitHub repository information, manage issues, and monitor workflow statuses through the GitHub REST API.-
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to access and query Garmin Connect health and fitness data, including sleep, HRV, training load, and activities, with an optional coaching plugin for personalized training plans.4-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to retrieve and discuss personal fitness activities, training splits, heart-rate zones, and daily health metrics from a Garmin Connect account.MIT
- AlicenseAqualityBmaintenanceEnables ChatGPT and compatible AI clients to query read-only Garmin Connect data—including sleep, HRV, heart rate, Body Battery, wellness metrics, and activities—through a hosted OAuth-backed MCP connection using a personal API key.2151MIT
- AlicenseNot gradedqualityBmaintenanceConnects AI agents to Garmin Connect so they can read fitness data (activities, sleep, steps, heart rate, weight, workouts, profile) and schedule or manage Garmin Calendar workouts with an explicit confirmation flow.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to review gym attendance, unsigned waivers, class reservations and belt ranks in a signed-in RhinoFit account, and to draft member communications. Requested write actions are shown for review and must be approved before they are applied.Elastic 2.0
TDQS
Scored across 17 tools
Most tools target clearly distinct resources or actions: single vs batch handicap lookup, roster CRUD, search, export, and connection management are well separated. The only mild ambiguity is between handicap history, recent scores, and recorded handicap changes, but the descriptions clarify different data sources and modes.
Tool names consistently use snake_case verb_noun patterns such as get_golfer_handicap, save_multiple_golfers, update_saved_golfer, and export_golfer_roster. The convention is predictable throughout, including connection tools like get_connection_status and disconnect_provider.
17 tools is slightly above the typical ideal range, but the surface spans lookup, roster management, history, export, deletion, and connection status, so most tools have a clear role. It is not excessively bloated for the domain, though a few lifecycle tools could potentially be consolidated.
The server covers the main lifecycle well: search, single and batch handicap lookup, save/update/remove saved golfers, refresh, change history, export, and roster deletion. Minor gaps remain around provider connection/login, since only status and disconnect are exposed, and course handicap calculation explicitly omits playing-handicap allowance.