caddie-mcp
Related Servers
Alternatives to caddie-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server that lets you ask questions about your Garmin training history in plain language. It ingests FIT files into DuckDB locally and exposes typed tools for analyzing activities, streams, and summaries.9MIT
- AlicenseAqualityBmaintenanceA Model Context Protocol (MCP) server for Garmin Connect integration. Access your activities, health data, training metrics, and more through Claude and other LLMs.2262MIT
- AlicenseNot gradedqualityBmaintenanceThis MCP server exposes Garmin Connect health data—sleep, heart rate, HRV, stress, VO2max, and activities—to Claude through local tools, enabling natural language queries, data syncing, and statistical analysis like correlations and night-out detection.MIT
- AlicenseNot gradedqualityBmaintenanceA local, single-user, read-only MCP server that gives Claude Code access to your Garmin health and training data, exposing tools for health snapshots, training status, run details, body metrics, and training analysis.1MIT
- AlicenseNot gradedqualityBmaintenanceA local, read-only MCP server that gives Claude access to your Garmin health and training data, exposing tools for health snapshots, training status, run details, body metrics, and training analysis.MIT
- AlicenseAqualityCmaintenanceMCP server that connects Garmin Connect to Claude Desktop, allowing users to query health and fitness data (sleep, workouts, heart rate, HRV, stress, Body Battery, etc.) in plain English and also log weight, hydration, and schedule workouts.25MIT
TDQS
Scored across 13 tools
Most tools have clearly distinct purposes, but get_round and get_shots both involve shot data, and query_golf_data could potentially retrieve anything. The descriptions do a good job of clarifying boundaries, so ambiguity is minimal.
Almost all tools follow the verb_noun pattern (get_*, sync_*, correlate_*, query_*), except garmin_status which is a noun phrase. This minor deviation is easily understood and does not undermine predictability.
With 13 tools, the server is well-scoped for a golf analytics platform. Each tool covers a distinct aspect of data ingestion, retrieval, analysis, and querying, without unnecessary bloat or thin coverage.
The tool set provides comprehensive coverage of the golf performance domain: syncing data, listing and inspecting rounds, shot-level details, stats (club, strokes gained, overall), handicap, course intelligence, health context, correlation analysis, and a general SQL query interface. No obvious dead ends or missing core operations.